admittedly
... this is not seem like silly coding bug, but weakness in the cryptography part. Which of course everyone assumed OpenSSL was doing right, despite other major flaws of the project ...
OpenSSL maintainers have pushed a pair of patches, crushing a dangerous but uncommon bug that allows HTTPS to be unravelled while also hardening servers against downgrade attacks. Affected servers are open to key recovery attacks only if it runs certain Digital Signature Algorithm and static Diffie-Hellman key exchange …
And I'll answer it... no it is not.
notepad.exe is also not vulnerable to the OpenSSL bugs, that doesn't make it particularly useful crypto library
(LibreSSL guys aim to not support even a tenth of the features that OpenSSL supports - anything outside very simple web hosting is "out of scope" for them)
OpenSSL should follow the example of CVEs and provide an "impact" rating to go with the "severity" rating. This one qualifies as severity HIGH, impact ZERO.
Took 20 minutes to figure out how to invoke the vulnerable code:
openssl genpkey -genparam -algorithm DSA -out dsap.pem -pkeyopt dsa_paramgen_bits:1024 -outform dh_rfc5114
The number of folks who have employed this are counted on one hand.