# CVE-2008-6005: Memory corruption in n/a

> Remote attackers can execute arbitrary code via buffer overflows in the CheckUniqueName function when processing duplicated attribute values.

- **Severity:** Critical 10.0 (`AV:N/AC:L/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:** 28 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pp86-pm93-fc5h

## What is CVE-2008-6005?

CVE-2008-6005 is a critical memory corruption vulnerability in n/a, published on 28 Jan 2009. 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

Multiple buffer overflows in the CheckUniqueName function in W3C Amaya Web Browser 10.0.1, and possibly other versions including 11.0.1, might allow remote attackers to execute arbitrary code via "duplicated" attribute value inputs.

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

## Which versions are affected by CVE-2008-6005?

It affects 1 product.


Products: W3c Amaya Web Browser.

## How do I fix CVE-2008-6005?

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

## Is CVE-2008-6005 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5282](https://insights.sbomify.com/CVE-2008-5282/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6005 and fix it if it is affected.

What it is: CVE-2008-6005 is a critical memory corruption vulnerability in n/a, published on 28 Jan 2009. 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-2008-6005 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-2008-6005/ (Markdown: https://insights.sbomify.com/CVE-2008-6005/index.md)
```

## Sources

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

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