CVE-2016-7055

Node.js 4 and 1 other: There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL…

CVE-2016-7055 is fixed in Node.js 4 on 1 platform by Node.js 4 4.7.3 (version 4.7.3), released January 31, 2017. 1 other affected product has no fix yet. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
5.9
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.1423
96th percentile

There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1.0.2 and 1.1.0 before 1.1.0c that handles input lengths divisible by, but longer than 256 bits. Analysis suggests that attacks against RSA, DSA and DH private keys are impossible. This is because the subroutine in question is not used in operations with the private key itself and an input of the attacker's direct choice. Otherwise the bug can manifest itself as transient authentication and key negotiation failures or reproducible erroneous outcome of public-key operations with specially crafted input. Among EC algorithms only Brainpool P-512 curves are affected and one presumably can attack ECDH key negotiation. Impact was not analyzed in detail, because pre-requisites for attack are considered unlikely. Namely multiple clients have to choose the curve in question and the server has to share the private key among them, neither of which is default behaviour. Even then only clients that chose the curve will be affected.

Where it's fixed

ProductFixed inFixReleased
Windows apps
Node.js 4 4.7.3 Node.js 4 4.7.3 Jan 31, 2017
No fix yet
Node.js 7 (Windows apps) No fix yet no-fix n/a

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.