# CVE-2024-1142: Sonatype IQ Server - Path Traversal

> Remote authenticated attackers can overwrite or delete files in Sonatype IQ Server via path traversal, requiring an upgrade to mitigate.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **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:** 6 Mar 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8v58-wvr2-fj59

## What is CVE-2024-1142?

CVE-2024-1142 is a medium-severity path traversal vulnerability in Sonatype IQ Server, published on 6 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Path Traversal in Sonatype IQ Server from version 143 allows remote authenticated attackers to overwrite or delete files via a specially crafted request. Version 171 fixes this issue.

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

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


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

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

## Is CVE-2024-1142 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1142 is a medium-severity path traversal vulnerability in Sonatype IQ Server, published on 6 Mar 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1142 in the wild and no public exploit code.

Affected product: Sonatype IQ Server. 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-2024-1142/ (Markdown: https://insights.sbomify.com/CVE-2024-1142/index.md)
```

## Sources

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

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