# CVE-2016-2108: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via crafted ASN.1 data in OpenSSL.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** DEBIAN-CVE-2016-2108, GHSA-cf8v-cq93-65gh, RHSA-2016:1137, UBUNTU-CVE-2016-2108

## What is CVE-2016-2108?

CVE-2016-2108 is a critical memory corruption vulnerability in Google Android, 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 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 denial of service (buffer underflow and memory corruption) via an ANY field in crafted serialized data, aka the "negative zero" issue.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 9 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl` | Red Hat:enterprise_linux:5::client | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-perl` | Red Hat:enterprise_linux:5::client | All versions | 0:0.9.8e-40.el5_11 |
| `openssl` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:0.9.8e-40.el5_11 |
| `openssl` | Red Hat:enterprise_linux:5::server | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:0.9.8e-40.el5_11 |
| `openssl-perl` | Red Hat:enterprise_linux:5::server | All versions | 0:0.9.8e-40.el5_11 |

Products: Google Android, Openssl Openssl, 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-2108?

Upgrade to a fixed version.

## Is CVE-2016-2108 being exploited?

There is no known exploitation of CVE-2016-2108 in the wild and no public exploit code.

## Other vulnerabilities in Google Android

- [CVE-2026-58704](https://insights.sbomify.com/CVE-2026-58704/): Google Pixel Improper Authorization (high 8.8, exploited in the wild)
- [CVE-2025-48543](https://insights.sbomify.com/CVE-2025-48543/): Android Runtime Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2023-35674](https://insights.sbomify.com/CVE-2023-35674/): Android Framework Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2025-48595](https://insights.sbomify.com/CVE-2025-48595/): Android Framework Integer Overflow (high 8.4, exploited in the wild)
- [CVE-2024-32896](https://insights.sbomify.com/CVE-2024-32896/): Android Pixel Privilege Escalation (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2108 is a critical memory corruption vulnerability in Google Android, published on 5 May 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2108 in the wild and no public exploit code.

Affected product: Google Android. 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-2108/ (Markdown: https://insights.sbomify.com/CVE-2016-2108/index.md)
```

## Sources

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

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