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

> Remote attackers can cause a crash or execute arbitrary code via a crafted JPEG image with a large component count in libjpeg-turbo.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Aug 2012
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-hh76-h9xr-wpjv

## What is CVE-2012-2806?

CVE-2012-2806 is a high-severity memory corruption vulnerability in n/a, published on 13 Aug 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the get_sos function in jdmarker.c in libjpeg-turbo 1.2.0 allows remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a large component count in the header of a JPEG image.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: D.r.commander Libjpeg-Turbo.

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

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

## Is CVE-2012-2806 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9614](https://insights.sbomify.com/CVE-2017-9614/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2806 is a high-severity memory corruption vulnerability in n/a, published on 13 Aug 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-2806 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-2806/ (Markdown: https://insights.sbomify.com/CVE-2012-2806/index.md)
```

## Sources

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

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