# CVE-2024-22232: Specially crafted url can be created which leads to a directory traversal in the salt file server

> A malicious user can read arbitrary files from the Salt master filesystem via a crafted URL, requiring an upgrade to mitigate.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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:** 27 Jun 2024
- **Updated:** 5 Nov 2024
- **Also known as:** GHSA-2qw3-2wv6-p64x, PYSEC-2026-1891, UBUNTU-CVE-2024-22232

## What is CVE-2024-22232?

CVE-2024-22232 is a high-severity path traversal vulnerability in VMware Salt Project, published on 27 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A specially crafted url can be created which leads to a directory traversal in the salt file server.
A malicious user can read an arbitrary file from a Salt master’s filesystem.

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

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

5 open source packages ship an affected version, including salt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `salt` | PyPI | All versions | 3005.5, 3006.6 |
| `salt` | PyPI | All versions | 3005.5 |
| `salt` | PyPI | All versions | 3005.5 |
| `salt` | PyPI | From 3006.0 | 3006.6 |
| `salt` | PyPI | From 3006.0 | 3006.6 |

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

Upgrade salt to a fixed version for your release line: 3005.5 or 3006.6.

## Is CVE-2024-22232 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22232 is a high-severity path traversal vulnerability in VMware Salt Project, published on 27 Jun 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-22232 in the wild and no public exploit code.

Affected packages and fixed versions:
- salt (PyPI): affected all versions; fixed in 3005.5, 3006.6
- salt (PyPI): affected all versions; fixed in 3005.5
- salt (PyPI): affected all versions; fixed in 3005.5
- salt (PyPI): affected from 3006.0; fixed in 3006.6
- salt (PyPI): affected from 3006.0; fixed in 3006.6

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

## Sources

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

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