# CVE-2016-1951: Integer overflow in n/a

> Remote attackers can cause denial of service or potential code execution via integer overflows in NSPR printf functions.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 7 Aug 2016
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2016-1951, DLA-513-1, DSA-3687-1, GHSA-2xc9-w6jv-x92w, UBUNTU-CVE-2016-1951, USN-3028-1

## What is CVE-2016-1951?

CVE-2016-1951 is a high-severity vulnerability in n/a, published on 7 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple integer overflows in io/prprf.c in Mozilla Netscape Portable Runtime (NSPR) before 4.12 allow remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via a long string to a PR_*printf function.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Mozilla Netscape Portable Runtime.

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

Upgrade to a fixed version.

## Is CVE-2016-1951 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1545](https://insights.sbomify.com/CVE-2014-1545/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1951 is a high-severity vulnerability in n/a, published on 7 Aug 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-1951 in the wild and no public exploit code.

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

## Sources

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

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