# CVE-2004-1438: Missing authorization in n/a

> Authenticated users with write access can read unauthorized repository parts via svn copy in the mod_authz_svn Apache module.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2004-1438, GHSA-w39v-wcwg-3989

## What is CVE-2004-1438?

CVE-2004-1438 is a low-severity missing authorization vulnerability in n/a, published on 13 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The mod_authz_svn Apache module for Subversion 1.0.4-r1 and earlier allows remote authenticated users, with write access to the repository, to read unauthorized parts of the repository via the svn copy command.

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

It affects 1 product.


Products: Subversion Subversion.

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

Upgrade to a fixed version.

## Is CVE-2004-1438 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2411](https://insights.sbomify.com/CVE-2009-2411/): Integer overflow in n/a (high 8.5)
- [CVE-2004-0397](https://insights.sbomify.com/CVE-2004-0397/): Memory corruption in n/a (high 7.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)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1438 is a low-severity missing authorization vulnerability in n/a, published on 13 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1438 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-1438/ (Markdown: https://insights.sbomify.com/CVE-2004-1438/index.md)
```

## Sources

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

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