CVE-2024-22231: Syndic cache directory creation is vulnerable to a directory traversal attack
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 53.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: VMware Salt Project 3005.5, 3006.6.
Low priority for now. Upgrade to VMware Salt Project 3005.5, 3006.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Syndic cache directory creation is vulnerable to a directory traversal attack in salt project which can lead a malicious attacker to create an arbitrary directory on a Salt master.
- Published
- Jun 27, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 53th percentile
- CWE
- CWE-22
Report tools
Action score
20
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · vmware
- 5.0
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.
VMware Salt Project
- before 3005.5, 3006.6affected · 3005.5, 3006.6
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.19 | salt | before 3006.6-r0 | 3006.6-r0 |
| openSUSE:Leap 15.5 | salt | before 3006.0-150500.4.29.1 | 3006.0-150500.4.29.1 |
| openSUSE:Leap Micro 5.3 | salt | before 3006.0-150400.8.54.1 | 3006.0-150400.8.54.1 |
| PyPI | salt | from 3006.0 · before 3006.6 | 3006.6 |
| PyPI | salt | before 3005.5 | 3005.5 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy | before 3.10.14-1.20.1 | 3.10.14-1.20.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-core | before 3.10.14-1.20.1 | 3.10.14-1.20.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-lxml | before 4.9.3-1.15.2 | 4.9.3-1.15.2 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | salt | before 3006.0-150100.117.1 | 3006.0-150100.117.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | salt | before 3006.0-150200.118.1 | 3006.0-150200.118.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | salt | before 3006.0-150300.53.70.1 | 3006.0-150300.53.70.1 |
| SUSE:Linux Enterprise Micro 5.3 | salt | before 3006.0-150400.8.54.1 | 3006.0-150400.8.54.1 |
| SUSE:Linux Enterprise Micro 5.5 | salt | before 3006.0-150500.4.29.1 | 3006.0-150500.4.29.1 |
| SUSE:Manager Client Tools 12 | venv-salt-minion | before 3006.0-3.52.3 | 3006.0-3.52.3 |
| SUSE:Manager Client Tools 15 | venv-salt-minion | before 3006.0-150000.3.54.3 | 3006.0-150000.3.54.3 |
| SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | venv-salt-minion | before 3006.0-1.36.3 | 3006.0-1.36.3 |
| SUSE:Manager Proxy 4.3 | release-notes-susemanager-proxy | before 4.3.11-150400.3.79.1 | 4.3.11-150400.3.79.1 |
| SUSE:Manager Server 4.3 | release-notes-susemanager | before 4.3.11-150400.3.100.1 | 4.3.11-150400.3.100.1 |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-22232Specially crafted url can be created which leads to a directory traversal in the salt file server30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| VMware Salt Project | 3005.5, 3006.6 | Vendor (CNA) |
| alpine:salt | 3006.6-r0 · Alpine:v3.19 | Package registry (OSV) |
| opensuse:salt | 3006.0-150400.8.54.1 · openSUSE:Leap Micro 5.3 | Package registry (OSV) |
| PyPI:salt | 3005.5 | Package registry (OSV) |
| PyPI:salt | 3006.6 | Package registry (OSV) |
| suse:release-notes-susemanager | 4.3.11-150400.3.100.1 · SUSE:Manager Server 4.3 | Package registry (OSV) |
| suse:release-notes-susemanager-proxy | 4.3.11-150400.3.79.1 · SUSE:Manager Proxy 4.3 | Package registry (OSV) |
| suse:salt | 3006.0-150100.117.1 · SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | Package registry (OSV) |
| suse:salt | 3006.0-150400.8.54.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:saltbundlepy | 3.10.14-1.20.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-core | 3.10.14-1.20.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-lxml | 4.9.3-1.15.2 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:venv-salt-minion | 3006.0-1.36.3 · SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-222320 days apartSpecially crafted url can be created which leads to a directory traversal in the salt file server30Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.