Skip to content
Noroxi
NVD / CVE Program· CNA redhat

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 allocation during a certain padding…

MediumCVSS 5.9 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Plan (action score 50/100)

  • Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 89% (FIRST EPSS); higher than 99.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: openssl (Alpine:v3.2) 1.0.2h-r0; openssl (Debian:12) 1.0.2h-1; openssl (Debian:7) 1.0.1e-2+deb7u21.

Add it to your regular patch cycle. Upgrade to openssl (Alpine:v3.2) 1.0.2h-r0; openssl (Debian:12) 1.0.2h-1; openssl (Debian:7) 1.0.1e-2+deb7u21 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 4, 2016
Updated
Jun 16, 2026
EPSS
89.0% · 99th percentile

Report tools

JSON

Action score

50

Plan

Add it to your regular patch cycle.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
27 / 30 · 89.0%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2016-2107

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Check your server's TLS configurationRun the SSL check

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Check your server's TLS configurationRun the SSL check

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
opensslopenssl
redhatenterprise linux desktop
redhatenterprise linux hpc node
redhatenterprise linux hpc node eus
redhatenterprise linux server
redhatenterprise linux server aus
redhatenterprise linux server eus
redhatenterprise linux workstation
opensuseleap
opensuseopensuse
googleandroid
hphelion openstack

and 3 more

Check your server's TLS configuration

The OpenSSL version can't be seen from outside; the free SSL checker tests your certificate, enabled TLS versions and weak ciphers. Confirm the version on your server with the package manager.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs node.js0.10.0 and later · before 0.10.45
  • nodejs node.js0.12.0 and later · before 0.12.14
  • nodejs node.js4.0.0 and later · up to 4.1.2 inclusive
  • nodejs node.js4.2.0 and later · before 4.4.4
  • nodejs node.js5.0.0 and later · before 5.11.1
  • nodejs node.js6.0.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.2opensslbefore 1.0.2h-r01.0.2h-r0
Debian:12opensslbefore 1.0.2h-11.0.2h-1
Debian:7opensslbefore 1.0.1e-2+deb7u211.0.1e-2+deb7u21
Debian:8opensslbefore 1.0.1k-3+deb8u51.0.1k-3+deb8u5
Red Hat:enterprise_linux:6::clientopensslbefore 0:1.0.1e-48.el6_8.10:1.0.1e-48.el6_8.1
Red Hat:enterprise_linux:6::clientopenssl-debuginfobefore 0:1.0.1e-48.el6_8.10:1.0.1e-48.el6_8.1
Red Hat:enterprise_linux:6::clientopenssl-develbefore 0:1.0.1e-48.el6_8.10:1.0.1e-48.el6_8.1
Red Hat:enterprise_linux:6::clientopenssl-perlbefore 0:1.0.1e-48.el6_8.10:1.0.1e-48.el6_8.1
Red Hat:enterprise_linux:6::clientopenssl-staticbefore 0:1.0.1e-48.el6_8.10:1.0.1e-48.el6_8.1
Red Hat:enterprise_linux:7::clientopensslbefore 1:1.0.1e-51.el7_2.51:1.0.1e-51.el7_2.5
Red Hat:enterprise_linux:7::clientopenssl-debuginfobefore 1:1.0.1e-51.el7_2.51:1.0.1e-51.el7_2.5
Red Hat:enterprise_linux:7::clientopenssl-develbefore 1:1.0.1e-51.el7_2.51:1.0.1e-51.el7_2.5
Red Hat:enterprise_linux:7::clientopenssl-libsbefore 1:1.0.1e-51.el7_2.51:1.0.1e-51.el7_2.5
Red Hat:enterprise_linux:7::clientopenssl-perlbefore 1:1.0.1e-51.el7_2.51:1.0.1e-51.el7_2.5
Red Hat:enterprise_linux:7::clientopenssl-staticbefore 1:1.0.1e-51.el7_2.51:1.0.1e-51.el7_2.5
Red Hat:rhel_eus:6.7::computenodeopensslbefore 0:1.0.1e-42.el6_7.50:1.0.1e-42.el6_7.5
Red Hat:rhel_eus:6.7::computenodeopenssl-debuginfobefore 0:1.0.1e-42.el6_7.50:1.0.1e-42.el6_7.5
Red Hat:rhel_eus:6.7::computenodeopenssl-develbefore 0:1.0.1e-42.el6_7.50:1.0.1e-42.el6_7.5
Red Hat:rhel_eus:6.7::computenodeopenssl-perlbefore 0:1.0.1e-42.el6_7.50:1.0.1e-42.el6_7.5
Red Hat:rhel_eus:6.7::computenodeopenssl-staticbefore 0:1.0.1e-42.el6_7.50:1.0.1e-42.el6_7.5
SUSE:Linux Enterprise Desktop 12opensslbefore 1.0.1i-27.16.11.0.1i-27.16.1
SUSE:Linux Enterprise Desktop 12 SP1opensslbefore 1.0.1i-47.11.0.1i-47.1
SUSE:Linux Enterprise Server 11-SECURITYopenssl1before 1.0.1g-0.47.11.0.1g-0.47.1

Other highest-scoring records for the same primary product.

  • CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows…KEV
    90Now
  • CVE-2021-3711SM2 Decryption Buffer Overflow
    65This week
  • CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code…
    65This week

Published before and after this one in the same product

  • ← EarlierCVE-2016-2105May 4, 2016 · Integer overflow in the EVP_EncodeUpdate function in crypto/evp/encode.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote…
    42Plan
  • ← EarlierCVE-2016-2106May 4, 2016 · Integer overflow in the EVP_EncryptUpdate function in crypto/evp/evp_enc.c in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h allows remote…
    38Monitor
  • Later →CVE-2016-2108May 4, 2016 · The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a…
    62This week

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:openssl1.0.2h-r0 · Alpine:v3.2Package registry (OSV)
debian:openssl1.0.2h-1 · Debian:12Package registry (OSV)
red hat:openssl1:1.0.1e-51.el7_2.5 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-debuginfo1:1.0.1e-51.el7_2.5 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-devel1:1.0.1e-51.el7_2.5 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-libs1:1.0.1e-51.el7_2.5 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-perl1:1.0.1e-51.el7_2.5 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:openssl-static1:1.0.1e-51.el7_2.5 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:openssl1.0.1i-27.16.1 · SUSE:Linux Enterprise Desktop 12Package registry (OSV)
suse:openssl11.0.1g-0.47.1 · SUSE:Linux Enterprise Server 11-SECURITYPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Exploit-DB entry ×1
  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Exploit-DB entrydos2016-05-04
Proof-of-concept repository on GitHubstars:1912016-05-03
Proof-of-concept repository on GitHubstars:22016-06-09

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. First PoC-2 d
  2. Published
  3. TodayNov 15, 2026+3846 d

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

References

All records