# CVE-2004-1903: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the blaxxun 3D plugin triggered by a malicious URL in an object tag.

- **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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xv5v-4g23-pxj9

## What is CVE-2004-1903?

CVE-2004-1903 is a critical memory corruption vulnerability in n/a, published on 10 May 2005. 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 blaxxun 3D 7.0 allows remote attackers to execute arbitrary code via a long URL property inside an object tag.

## Which versions are affected by CVE-2004-1903?

It affects 1 product.


Products: Blaxxun Contact 3d.

## How do I fix CVE-2004-1903?

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

## Is CVE-2004-1903 being exploited?

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

Public exploit code:

- Blaxxun Contact 3D - X-CC3D Browser Object Buffer Overflow (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1903 and fix it if it is affected.

What it is: CVE-2004-1903 is a critical memory corruption vulnerability in n/a, published on 10 May 2005. 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-2004-1903 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-2004-1903/ (Markdown: https://insights.sbomify.com/CVE-2004-1903/index.md)
```

## Sources

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

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