# CVE-2012-2114: Memory corruption in n/a

> A stack-based buffer overflow in musl's fprintf allows attackers to cause crashes or execute arbitrary code via long strings.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xm6q-pww3-56gm

## What is CVE-2012-2114?

CVE-2012-2114 is a high-severity memory corruption vulnerability in n/a, published on 31 Aug 2012. 

### Official description

Stack-based buffer overflow in fprintf in musl before 0.8.8 and earlier allows context-dependent attackers to cause a denial of service (crash) or possibly execute arbitrary code via a long string to an unbuffered stream such as stderr.

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

## Which versions are affected by CVE-2012-2114?

It affects 1 product.


Products: Etalabs Musl.

## How do I fix CVE-2012-2114?

No fix has been published for CVE-2012-2114 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-2114 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8859](https://insights.sbomify.com/CVE-2016-8859/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2114 and fix it if it is affected.

What it is: CVE-2012-2114 is a high-severity memory corruption vulnerability in n/a, published on 31 Aug 2012. 
Exploitation: There is no known exploitation of CVE-2012-2114 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-2012-2114/ (Markdown: https://insights.sbomify.com/CVE-2012-2114/index.md)
```

## Sources

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

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