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

> Remote attackers can execute arbitrary code via a buffer overflow in Libxml2's nanohttp or nanoftp modules using a long URL.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** Not needed
- **Fix available:** Yes
- **Published:** 4 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0110, DSA-455, GHSA-rvch-8g97-9qch, RHSA-2004:090

## What is CVE-2004-0110?

CVE-2004-0110 is a high-severity memory corruption vulnerability in Sgi Propack, published on 4 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the (1) nanohttp or (2) nanoftp modules in XMLSoft Libxml 2 (Libxml2) 2.6.0 through 2.6.5 allow remote attackers to execute arbitrary code via a long URL.

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

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libxml2` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5.10-6 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5.10-6 |
| `libxml2-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5.10-6 |
| `libxml2-python` | Red Hat:enterprise_linux:3::as | All versions | 0:2.5.10-6 |
| `libxml2` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5.10-6 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5.10-6 |
| `libxml2-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5.10-6 |
| `libxml2-python` | Red Hat:enterprise_linux:3::desktop | All versions | 0:2.5.10-6 |
| `libxml2` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5.10-6 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5.10-6 |
| `libxml2-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5.10-6 |
| `libxml2-python` | Red Hat:enterprise_linux:3::es | All versions | 0:2.5.10-6 |
| `libxml2` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5.10-6 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5.10-6 |
| `libxml2-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5.10-6 |
| `libxml2-python` | Red Hat:enterprise_linux:3::ws | All versions | 0:2.5.10-6 |

Products: Sgi Propack, Xmlsoft Libxml, Xmlsoft Libxml2.

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

Upgrade to a fixed version.

## Is CVE-2004-0110 being exploited?

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

Public exploit code:

- libxml 2.6.12 nanoftp - Local Buffer Overflow (exploitdb)

## Other vulnerabilities in Sgi Propack

- [CVE-2004-0521](https://insights.sbomify.com/CVE-2004-0521/): SQL injection in n/a (critical 10.0)
- [CVE-2005-1859](https://insights.sbomify.com/CVE-2005-1859/): Privilege escalation in n/a (high 7.2)
- [CVE-2004-0148](https://insights.sbomify.com/CVE-2004-0148/): Auth bypass in n/a (high 7.2)
- [CVE-2004-0519](https://insights.sbomify.com/CVE-2004-0519/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2004-0233](https://insights.sbomify.com/CVE-2004-0233/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0110 is a high-severity memory corruption vulnerability in Sgi Propack, published on 4 Mar 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0110 exists.

Affected product: Sgi Propack. 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-0110/ (Markdown: https://insights.sbomify.com/CVE-2004-0110/index.md)
```

## Sources

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

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