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

> A format string vulnerability in Dia allows attackers to cause a crash or execute arbitrary code via crafted filenames or diagram files.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 19 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2006-2480, GHSA-prr8-97x3-2662

## What is CVE-2006-2480?

CVE-2006-2480 is a medium-severity memory corruption vulnerability in n/a, published on 19 May 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

Format string vulnerability in Dia 0.94 allows user-assisted attackers to cause a denial of service (crash) and possibly execute arbitrary code by triggering errors or warnings, as demonstrated via format string specifiers in a .bmp filename.  NOTE: the original exploit was demonstrated through a command line argument, but there are other mechanisms for input that are automatically processed by Dia, such as a crafted .dia file.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Dia Dia.

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

Upgrade to a fixed version.

## Is CVE-2006-2480 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2480 exists.

Public exploit code:

- Dia 0.8x/0.9x - Filename Remote Format String (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-1550](https://insights.sbomify.com/CVE-2006-1550/): Memory corruption in n/a (high 7.6)
- [CVE-2007-3408](https://insights.sbomify.com/CVE-2007-3408/): Memory corruption in n/a (high 7.5)
- [CVE-2006-2453](https://insights.sbomify.com/CVE-2006-2453/): Other in n/a (high 7.5)
- [CVE-2008-5984](https://insights.sbomify.com/CVE-2008-5984/): Code injection in n/a (medium 6.9)
- [CVE-2005-2966](https://insights.sbomify.com/CVE-2005-2966/): Command injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-2480 is a medium-severity memory corruption vulnerability in n/a, published on 19 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2480 exists.

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-2480/ (Markdown: https://insights.sbomify.com/CVE-2006-2480/index.md)
```

## Sources

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

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