# CVE-2016-2107: Information disclosure in n/a

> Remote attackers can obtain sensitive cleartext information via a padding-oracle attack against AES CBC sessions using the vulnerable OpenSSL library.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2016
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2016-2107, DEBIAN-CVE-2016-2107, GHSA-3gm7-8cfv-p8h9, UBUNTU-CVE-2016-2107

## What is CVE-2016-2107?

CVE-2016-2107 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 5 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-310, CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-2107?

It affects 15 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Google Android, Hp Helion Openstack, Nodejs Node.js, Openssl Openssl, Opensuse Leap, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Hpc Node, Redhat Enterprise Linux Hpc Node Eus, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus, Redhat Enterprise Linux Workstation.

## How do I fix CVE-2016-2107?

Upgrade to a fixed version.

## Is CVE-2016-2107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-2107 exists.

Public exploit code:

- Simple test for the May 2016 OpenSSL padding oracle (CVE-2016-2107) (github_poc): https://github.com/FiloSottile/CVE-2016-2107
- Docker container implementing tests for CVE-2016-2107 - LuckyNegative20 (github_poc): https://github.com/tmiklas/docker-cve-2016-2107
- OpenSSL - Padding Oracle in AES-NI CBC MAC Check (exploitdb)

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2107 and fix it if it is affected.

What it is: CVE-2016-2107 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 5 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-2107 exists.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-2107/ (Markdown: https://insights.sbomify.com/CVE-2016-2107/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-2107
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-2107
- OSV: https://osv.dev/vulnerability/CVE-2016-2107

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-2107/
Summaries are generated and may contain mistakes; the official description above is the record.