CVE-2024-38825: CVE-2024-38825 Salt Advisory
Noroxi assessment
Priority: Monitor (action score 25/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.15% (FIRST EPSS).
- 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 3006.12, 3007.4.
Low priority for now. Upgrade to VMware SALT 3006.12, 3007.4 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
The salt.auth.pki module does not properly authenticate callers. The "password" field contains a public certificate which is validated against a CA certificate by the module. This is not pki authentication, as the caller does not need access to the corresponding private key for the authentication attempt to be accepted.
- BDU:2025-10849
- GHSA-4j59-vv55-q6h3
- openSUSE-SU-2025:15295-1
- PYSEC-2026-1893
- SUSE-EL-9-CLIENT-TOOLS-2025-2499
- SUSE-SU-2025:02476-1
- SUSE-SU-2025:02491-1
- SUSE-SU-2025:02492-1
- SUSE-SU-2025:02499-1
- SUSE-SU-2025:02500-1
- SUSE-SU-2025:02501-1
- SUSE-SU-2025:02502-1
- SUSE-SU-2025:02534-1
- SUSE-SU-2025:20487-1
- SUSE-SU-2025:20504-1
- Published
- Jun 13, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- CWE-287
Report tools
Action score
25
Monitor
Low priority for now.
- CVSS
- 25 / 40 · 6.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · vmware
- 6.4
- 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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 3006.x and later · before 3006.12affected · lts
- 3007.x and later · before 3007.4affected · sts
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.6 | salt | before 3006.0-150500.4.55.1 | 3006.0-150500.4.55.1 |
| openSUSE:Leap 15.6 | salt-test | before 3006.0-150500.4.55.1 | 3006.0-150500.4.55.1 |
| openSUSE:Tumbleweed | salt | before 3006.0-41.1 | 3006.0-41.1 |
| PyPI | salt | from 3006.0rc1 · before 3006.12 | 3006.12 |
| PyPI | salt | from 3007.0rc1 · before 3007.4 | 3007.4 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy | before 3.11.11-1.32.1 | 3.11.11-1.32.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-core | before 3.11.11-1.32.1 | 3.11.11-1.32.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-cython | before 0.29.37-1.12.2 | 0.29.37-1.12.2 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-jinja2 | before 3.1.2-1.12.2 | 3.1.2-1.12.2 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-lxml | before 4.9.4-1.21.1 | 4.9.4-1.21.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-m2crypto | before 0.45.1-1.12.1 | 0.45.1-1.12.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-msgpack | before 1.0.7-1.14.1 | 1.0.7-1.14.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-ply | before 3.11-1.8.1 | 3.11-1.8.1 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-tornado | before 6.3.2-1.12.2 | 6.3.2-1.12.2 |
| SUSE:EL-9:Update:Products:SaltBundle:Update | saltbundlepy-zypp-plugin | before 0.6.5-1.11.1 | 0.6.5-1.11.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | salt | before 3006.0-150300.53.94.1 | 3006.0-150300.53.94.1 |
| SUSE:Linux Enterprise Micro 5.3 | salt | before 3006.0-150400.8.80.1 | 3006.0-150400.8.80.1 |
| SUSE:Linux Enterprise Micro 5.5 | salt | before 3006.0-150500.4.55.1 | 3006.0-150500.4.55.1 |
| SUSE:Linux Enterprise Module for Systems Management 15 SP7 | salt | before 3006.0-150700.14.5.2 | 3006.0-150700.14.5.2 |
| SUSE:Linux Micro 6.0 | salt | before 3006.0-13.1 | 3006.0-13.1 |
| SUSE:Linux Micro 6.1 | salt | before 3006.0-slfo.1.1_4.1 | 3006.0-slfo.1.1_4.1 |
| SUSE:Manager Client Tools 12 | venv-salt-minion | before 3006.0-3.76.2 | 3006.0-3.76.2 |
| SUSE:Manager Client Tools 15 | venv-salt-minion | before 3006.0-150000.3.78.1 | 3006.0-150000.3.78.1 |
| SUSE:Manager Client Tools for RHEL, Liberty and Clones 9-CLIENT-TOOLS | venv-salt-minion | before 3006.0-1.59.1 | 3006.0-1.59.1 |
+2
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-22239CVE-2025-22239 salt advisory32Monitor
- CVE-2025-22236CVE-2025-22236 salt advisory32Monitor
- CVE-2025-22237CVE-2025-22237 salt advisory26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-38822Jun 13, 2025 · CVE-2024-38822 Salt Advisory10Monitor
- ← EarlierCVE-2024-38823Jun 13, 2025 · CVE-2024-38823 Salt Advisory10Monitor
- Later →CVE-2025-22238Jun 13, 2025 · CVE-2025-22238 salt advisory16Monitor
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 | 3006.12 | Vendor (CNA) |
| VMware SALT | 3007.4 | Vendor (CNA) |
| opensuse:salt | 3006.0-150500.4.55.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:salt-test | 3006.0-150500.4.55.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| PyPI:salt | 3006.12 | Package registry (OSV) |
| PyPI:salt | 3007.4 | Package registry (OSV) |
| suse:release-notes-susemanager | 4.3.16-150400.3.140.1 · SUSE:Manager Server 4.3 | Package registry (OSV) |
| suse:release-notes-susemanager-proxy | 4.3.16-150400.3.98.1 · SUSE:Manager Proxy 4.3 | Package registry (OSV) |
| suse:salt | 3006.0-150500.4.55.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:saltbundlepy | 3.11.11-1.32.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-core | 3.11.11-1.32.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-cython | 0.29.37-1.12.2 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-jinja2 | 3.1.2-1.12.2 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-lxml | 4.9.4-1.21.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-m2crypto | 0.45.1-1.12.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-msgpack | 1.0.7-1.14.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-ply | 3.11-1.8.1 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:saltbundlepy-tornado | 6.3.2-1.12.2 · SUSE:EL-9:Update:Products:SaltBundle:Update | Package registry (OSV) |
| suse:venv-salt-minion | 3006.0-1.59.1 · 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-222360 days apartCVE-2025-22236 salt advisory32Monitor
- CVE-2024-388220 days apartCVE-2024-38822 Salt Advisory10Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
- CVE-2025-222370 days apartCVE-2025-22237 salt advisory26Monitor
- CVE-2025-222400 days apartCVE-2025-22240 salt advisory25Monitor
- CVE-2025-222410 days apartCVE-2025-22241 salt advisory22Monitor
- CVE-2025-222380 days apartCVE-2025-22238 salt advisory16Monitor
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- low · data can be read
- 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
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
nvd-secondary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.