CVE-2017-3736

libssl1.0.0: There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 befor...

CVE-2017-3736 is fixed in 2 products on 1 platform, first by libssl1.0.0 1.0.2g-1ubuntu14, released November 1, 2017. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
Medium
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.1013
95th percentile

There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. 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. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.

Where it's fixed

ProductFixed inFixReleased
Linux
libssl1.0.0 · Ubuntu 18.04.6 LTS (bionic) 1.0.2g-1ubuntu14 libssl1.0.0 1.0.2g-1ubuntu14 Nov 1, 2017
openssl · Ubuntu 18.04.6 LTS (bionic) 1.0.2g-1ubuntu14 openssl 1.0.2g-1ubuntu14 Nov 1, 2017

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.