# CVE-2006-1060: Memory corruption in n/a

> Heap-based buffer overflow in zgv and xzgv allows arbitrary code execution via malicious JPEG images with specific color spaces.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-1060, DSA-1037-1, DSA-1038-1, GHSA-9p54-cf8m-jj22, openSUSE-SU-2024:10151-1

## What is CVE-2006-1060?

CVE-2006-1060 is a high-severity memory corruption vulnerability in n/a, published on 11 Apr 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in zgv before 5.8 and xzgv before 0.8 might allow user-assisted attackers to execute arbitrary code via a JPEG image with more than 3 output components, such as a CMYK or YCCK color space, which causes less memory to be allocated than required.

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

## Which versions are affected by CVE-2006-1060?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xzgv` | openSUSE:Tumbleweed | All versions | 0.9.1-27.8 |

Products: Xzgv Xzgv.

## How do I fix CVE-2006-1060?

Upgrade to a fixed version.

## Is CVE-2006-1060 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1060 and fix it if it is affected.

What it is: CVE-2006-1060 is a high-severity memory corruption vulnerability in n/a, published on 11 Apr 2006. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2006-1060 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-2006-1060/ (Markdown: https://insights.sbomify.com/CVE-2006-1060/index.md)
```

## Sources

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

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