# CVE-2024-38822: CVE-2024-38822 Salt Advisory

> A misbehaving minion can impersonate another minion due to skipped token validation, allowing unauthorized access and potential privilege escalation.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-5m5v-pwj7-rj26, UBUNTU-CVE-2024-38822

## What is CVE-2024-38822?

CVE-2024-38822 is a low-severity authentication bypass vulnerability in VMware SALT, published on 13 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Multiple methods in the salt master skip minion token validation. Therefore a misbehaving minion can impersonate another minion.

Weakness: CWE-287 (Improper Authentication)

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


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

Apply the vendor's patch.

## Is CVE-2024-38822 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38822 is a low-severity authentication bypass vulnerability in VMware SALT, published on 13 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38822 in the wild and no public exploit code.

Affected product: VMware SALT. 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-38822/ (Markdown: https://insights.sbomify.com/CVE-2024-38822/index.md)
```

## Sources

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

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