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

> Remote attackers can execute arbitrary code by tricking users into opening a malicious DeepBurner file with a long filename.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** 20 Dec 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r4mf-gv8v-r25g

## What is CVE-2006-6665?

CVE-2006-6665 is a medium-severity memory corruption vulnerability in n/a, published on 20 Dec 2006. 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

Buffer overflow in Astonsoft DeepBurner Pro and Free 1.8.0 and earlier allows user-assisted remote attackers to execute arbitrary code via a long file name tag in a dbr file.

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

It affects 1 product.


Products: Astonsoft Deepburner.

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

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

## Is CVE-2006-6665 being exploited?

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

Public exploit code:

- AstonSoft DeepBurner 1.8.0 - '.dbr' File Parsing Buffer Overflow (exploitdb)
- AstonSoft DeepBurner (DBR File) Path Buffer Overflow (metasploit)
- AstonSoft DeepBurner - '.dbr' Path Buffer Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6665 is a medium-severity memory corruption vulnerability in n/a, published on 20 Dec 2006. An attacker can exploit it over the internet without logging in, 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-6665 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-6665/ (Markdown: https://insights.sbomify.com/CVE-2006-6665/index.md)
```

## Sources

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

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