# CVE-2007-5731: Path traversal in n/a

> Authenticated remote attackers can read arbitrary files via WebDAV write requests exploiting a path traversal flaw in Apache Jakarta Slide.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** No
- **Published:** 30 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h7f5-5qw4-27g2

## What is CVE-2007-5731?

CVE-2007-5731 is a low-severity path traversal vulnerability in n/a, published on 30 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Absolute path traversal vulnerability in Apache Jakarta Slide 2.1 and earlier allows remote authenticated users to read arbitrary files via a WebDAV write request that specifies an entity with a SYSTEM tag, a related issue to CVE-2007-5461.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2007-5731?

It affects 1 product.


Products: Apache Jakarta Slide.

## How do I fix CVE-2007-5731?

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

## Is CVE-2007-5731 being exploited?

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

Public exploit code:

- Jakarta Slide 2.1 RC1 - Remote File Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5731 and fix it if it is affected.

What it is: CVE-2007-5731 is a low-severity path traversal vulnerability in n/a, published on 30 Oct 2007. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-5731 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-2007-5731/ (Markdown: https://insights.sbomify.com/CVE-2007-5731/index.md)
```

## Sources

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

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