LiveActive security incident?Get immediate response
CVE Record

CVE-2016-2107: The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocat...

The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a certain padding check, which allows remote attackers to obtain sensitive cleartext information via a padding-oracle attack against an AES CBC session. NOTE: this vulnerability exists because of an incorrect fix for CVE-2013-0169.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This OpenSSL flaw can let a remote attacker recover sensitive plaintext from AES-CBC encrypted sessions by abusing a padding-oracle weakness. It affects older OpenSSL 1.0.1 and 1.0.2 releases before the named fixed versions. Treat internet-facing TLS services and embedded appliances using those builds as priority review items. Exposure is most likely on servers, appliances, or applications using vulnerable OpenSSL 1.0.1 or 1.0.2 builds with AES-NI and AES-CBC sessions. The provided structured affected-product list is incomplete, so product-specific exposure requires local inventory and vendor advisory checks. Prioritize remediation where vulnerable OpenSSL supports public-facing or sensitive-data TLS traffic. This is not described as code execution, but plaintext recovery can directly affect confidentiality and compliance obligations. Mitigation focus: Upgrade OpenSSL to 1.0.1t, 1.0.2h, or a vendor-patched supported release.; Apply relevant operating system or appliance vendor advisories for bundled OpenSSL packages.; Prioritize internet-facing TLS services and products handling sensitive data..

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-2107 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
15Source links

CVSS and timeline data

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

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.