LiveActive security incident?Get immediate response
CVE Record

CVE-2016-7055: There is a carry propagating bug in the Broadwell-specific Montgomery multiplication procedure in OpenSSL 1...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2016-7055 is a narrow OpenSSL math bug affecting some public-key operations on Broadwell-specific code paths. The source analysis says attacks against RSA, DSA, and DH private keys are impossible, but authentication or key negotiation may fail under crafted inputs. Business urgency is mainly patch hygiene for systems still carrying old OpenSSL builds. Exposure is most plausible on legacy systems using affected OpenSSL versions, especially vendor-packaged or statically linked software. The issue is architecture and algorithm dependent, so normal OpenSSL presence alone does not prove practical exposure. Downstream advisories from Red Hat, FreeBSD, Gentoo, Oracle, HPE, and Tenable indicate broad vendor tracking. Treat this as a legacy crypto-library remediation item, not an emergency, unless critical systems still run affected OpenSSL builds. Prioritize internet-facing authentication, TLS termination, VPN, and appliance estates where vendor patches may lag or bundled OpenSSL is hard to see. Mitigation focus: Upgrade OpenSSL 1.1.0 deployments to 1.1.0c or later.; Apply vendor security updates for affected operating systems and appliances.; Check vendor guidance for OpenSSL 1.0.2 package-specific fixes..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-7055 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
11Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.