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

> Remote attackers can execute arbitrary code via stack-based buffer overflow in Subversion's time conversion during DAV2 or svn-protocol requests.

- **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:** 28 May 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-0397, GHSA-vwxm-8m4v-97wg

## What is CVE-2004-0397?

CVE-2004-0397 is a high-severity memory corruption vulnerability in n/a, published on 28 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack-based buffer overflow during the apr_time_t data conversion in Subversion 1.0.2 and earlier allows remote attackers to execute arbitrary code via a (1) DAV2 REPORT query or (2) get-dated-rev svn-protocol command.

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

It affects 1 product.


Products: Subversion Subversion.

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

Upgrade to a fixed version.

## Is CVE-2004-0397 being exploited?

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

Public exploit code:

- Subversion 1.0.2 - Date Overflow (Metasploit) (exploitdb)
- Subversion Date Svnserve (metasploit)
- Subversion 1.0.2 - 'svn_time_from_cstring()' Remote Overflow (exploitdb)
- Subversion - Date Svnserve (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2411](https://insights.sbomify.com/CVE-2009-2411/): Integer overflow in n/a (high 8.5)
- [CVE-2007-3846](https://insights.sbomify.com/CVE-2007-3846/): Path traversal in n/a (medium 6.0)
- [CVE-2007-2448](https://insights.sbomify.com/CVE-2007-2448/): Information disclosure in n/a (low 2.1)
- [CVE-2004-1438](https://insights.sbomify.com/CVE-2004-1438/): Missing authorization in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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