There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL 1.0.2 prior to 1.0.2k and 1.1.0 prior to 1.1.0d. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. For example this can occur by default in OpenSSL DHE based SSL/TLS ciphersuites. Note: This issue is very similar to CVE-2015-3193 but must be treated as a separate problem.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
openssl openssl 1.0.2a |
||
openssl openssl 1.0.2e |
||
openssl openssl 1.0.2b |
||
openssl openssl 1.1.0c |
||
openssl openssl 1.0.2h |
||
openssl openssl 1.0.2c |
||
openssl openssl 1.1.0b |
||
openssl openssl 1.0.2 |
||
openssl openssl 1.1.0a |
||
openssl openssl 1.0.2f |
||
openssl openssl 1.0.2i |
||
openssl openssl 1.0.2d |
||
nodejs node.js |
One was fixed before anyone realised it was a security issue, so be careful when applying
OpenSSL's released patches for a trio of denial-of-service bugs. The first (CVE-2017-3731), turned up by Google's Robert Święcki, only affects SSL/TLS servers running on 32-bit hosts. Depending on the cipher the host is using, a truncated packet crashes the system by triggering an out-of-bounds read. It's version-specific: under OpenSSL 1.1.0 the relevant cipher is CHACHA20/POLY1305 and it's fixed in 1.1.0d. In OpenSSL 1.0.2, RC4-MD5 (which should have been disabled) is the target, and it's fi...
Vulmon