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

> Remote attackers can execute arbitrary code via buffer overflows in W3C Amaya when processing malicious HTML attributes, requiring user interaction to view the content.

- **Severity:** High 7.6 (`AV:N/AC:H/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:** 20 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gg2r-jxgr-8f34

## What is CVE-2006-1900?

CVE-2006-1900 is a high-severity memory corruption vulnerability in n/a, published on 20 Apr 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

Multiple buffer overflows in World Wide Web Consortium (W3C) Amaya 9.4, and possibly other versions including 8.x before 8.8.5, allow remote attackers to execute arbitrary code via a long value in (1) the COMPACT attribute of the COLGROUP element, (2) the ROWS attribute of the TEXTAREA element, and (3) the COLOR attribute of the LEGEND element; and via other unspecified attack vectors consisting of "dozens of possible snippets."

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

It affects 1 product.


Products: W3c Amaya.

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

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

## Is CVE-2006-1900 being exploited?

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

Public exploit code:

- W3C Amaya 9.4 - textarea rows Attribute Value Overflow (exploitdb)
- W3C Amaya 9.4 - legend color Attribute Value Overflow (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-1900 is a high-severity memory corruption vulnerability in n/a, published on 20 Apr 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-1900 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-1900/ (Markdown: https://insights.sbomify.com/CVE-2006-1900/index.md)
```

## Sources

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

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