# CVE-2024-42499: FitNesse Path Traversal

> Attackers can determine file existence and read partial file contents via path traversal in FitNesse.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-q297-5ff8-hc92

## What is CVE-2024-42499?

CVE-2024-42499 is a medium-severity path traversal vulnerability in unclebob FitNesse, published on 15 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper limitation of a pathname to a restricted directory ('Path Traversal') issue exists in FitNesse releases prior to 20241026. If this vulnerability is exploited, an attacker may be able to know whether a file exists at a specific path, and/or obtain some part of the file contents under specific conditions.

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

## Which versions are affected by CVE-2024-42499?

2 open source packages ship an affected version, including org.fitnesse:fitnesse.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.fitnesse:fitnesse` | Maven | All versions | 20241026 |
| `org.fitnesse:fitnesse` | Maven | All versions | 20241026 |

## How do I fix CVE-2024-42499?

Upgrade org.fitnesse:fitnesse to 20241026 or later.

## Is CVE-2024-42499 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42499 and fix it if it is affected.

What it is: CVE-2024-42499 is a medium-severity path traversal vulnerability in unclebob FitNesse, published on 15 Nov 2024. 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-2024-42499 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.fitnesse:fitnesse (Maven): affected all versions; fixed in 20241026
- org.fitnesse:fitnesse (Maven): affected all versions; fixed in 20241026

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-2024-42499/ (Markdown: https://insights.sbomify.com/CVE-2024-42499/index.md)
```

## Sources

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

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