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

> Remote attackers can execute arbitrary code via a crafted DjVu file in the Caminova DjVu Browser Plug-in, requiring user interaction to open the file.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Sep 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7pmf-w3wx-qjc6

## What is CVE-2012-5006?

CVE-2012-5006 is a critical memory corruption vulnerability in n/a, published on 19 Sep 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 npdjvu.dll in Caminova DjVu Browser Plug-in 6.1.4 Build 27351 and other versions before 6.1.4.27993 allows remote attackers to execute arbitrary code via a crafted Sjbz chunk in a djvu file.

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

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

It affects 1 product.


Products: Caminova Djvu Browser Plug-In.

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

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

## Is CVE-2012-5006 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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