# CVE-2004-0413: Integer overflow in n/a

> Remote attackers can cause denial of service or execute arbitrary code via integer overflow in Subversion's svn protocol handling.

- **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:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0413, GHSA-hwr7-hw2w-cf69

## What is CVE-2004-0413?

CVE-2004-0413 is a critical vulnerability in n/a, published on 23 Jun 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libsvn_ra_svn in Subversion 1.0.4 trusts the length field of (1) svn://, (2) svn+ssh://, and (3) other svn protocol URL strings, which allows remote attackers to cause a denial of service (memory consumption) and possibly execute arbitrary code via an integer overflow that leads to a heap-based buffer overflow.

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

It affects 2 products.


Products: Openpkg Openpkg, Subversion Subversion.

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

Upgrade to a fixed version.

## Is CVE-2004-0413 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1019](https://insights.sbomify.com/CVE-2004-1019/): Deserialization in n/a (critical 10.0)
- [CVE-2004-1065](https://insights.sbomify.com/CVE-2004-1065/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0985](https://insights.sbomify.com/CVE-2002-0985/): Command injection in n/a (high 7.5)
- [CVE-2004-0957](https://insights.sbomify.com/CVE-2004-0957/): Privilege escalation in n/a (medium 6.8)
- [CVE-2003-0147](https://insights.sbomify.com/CVE-2003-0147/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0413 is a critical vulnerability in n/a, published on 23 Jun 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0413 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-2004-0413/ (Markdown: https://insights.sbomify.com/CVE-2004-0413/index.md)
```

## Sources

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

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