# CVE-2014-1545: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via out-of-bounds write in Mozilla NSPR sprintf and console functions.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-1545, DLA-32-1, DSA-2962-1, GHSA-r364-qw2p-cpfx, UBUNTU-CVE-2014-1545, USN-2265-1

## What is CVE-2014-1545?

CVE-2014-1545 is a critical memory corruption vulnerability in n/a, published on 11 Jun 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mozilla Netscape Portable Runtime (NSPR) before 4.10.6 allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds write) via vectors involving the sprintf and console functions.

## Which versions are affected by CVE-2014-1545?

It affects 1 product.


Products: Mozilla Netscape Portable Runtime.

## How do I fix CVE-2014-1545?

Upgrade to a fixed version.

## Is CVE-2014-1545 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-1951](https://insights.sbomify.com/CVE-2016-1951/): Integer overflow in n/a (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1545 and fix it if it is affected.

What it is: CVE-2014-1545 is a critical memory corruption vulnerability in n/a, published on 11 Jun 2014. 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-2014-1545 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-2014-1545/ (Markdown: https://insights.sbomify.com/CVE-2014-1545/index.md)
```

## Sources

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

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