CVE-2016-7055

MEDIUM
5.9
CVSS Score
Published: May 4, 2017 at 08:00 PM UTC
Updated: June 17, 2026 at 12:52 AM UTC
2 products affected across 2 vendorsOpenSSLNode.js

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 14%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.0.0 ≤ v ≤ 4.1.24.2.0 ≤ v < 4.7.36.0.0 ≤ v ≤ 6.8.16.9.0 ≤ v < 6.9.57.0.0 ≤ v < 7.5.0
Affected range stops below 4.7.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.9.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.5.0, so it looks safe — our inference, not a vendor statement
1.0.2 ≤ v < 1.0.2k1.1.0 ≤ v < 1.1.0c
Affected range stops below 1.0.2k, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.0c, so it looks safe — our inference, not a vendor statement

References (15)

VDB Entryx_refsource_BIDThird Party AdvisoryUS Government Resource
http://www.securityfocus.com/bid/94242
VDB Entryx_refsource_SECTRACKThird Party Advisory
http://www.securitytracker.com/id/1037261
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2018:2185
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2018:2186
Vendor Advisoryx_refsource_REDHATThird Party Advisory
https://access.redhat.com/errata/RHSA-2018:2187

CVSS

Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card