CVE-2021-25315: salt-api unauthenticated remote code execution
Noroxi assessment
Priority: Monitor (action score 32/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: 2.2% (FIRST EPSS); higher than 83.4% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: salt (openSUSE:Leap 15.2) 3002.2-lp152.3.36.1; python-distro (openSUSE:Leap 15.3) 1.5.0-3.5.1; salt (PyPI) 3002.2.
- Severity is disputed: the assigning authority (CNA) scores it 9.8, NVD 7.8.
Low priority for now. Upgrade to salt (openSUSE:Leap 15.2) 3002.2-lp152.3.36.1; python-distro (openSUSE:Leap 15.3) 1.5.0-3.5.1; salt (PyPI) 3002.2 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
CWE - CWE-287: Improper Authentication vulnerability in SUSE Linux Enterprise Server 15 SP 3; openSUSE Tumbleweed allows local attackers to execute arbitrary code via salt without the need to specify valid credentials. This issue affects: SUSE Linux Enterprise Server 15 SP 3 salt versions prior to 3002.2-3. openSUSE Tumbleweed salt version 3002.2-2.1 and prior versions. This issue affects: SUSE Linux Enterprise Server 15 SP 3 salt versions prior to 3002.2-3. openSUSE Tumbleweed salt version 3002.2-2.1 and prior versions.
- Published
- Mar 3, 2021
- Updated
- Jun 16, 2026
- EPSS
- 2.2% · 83th percentile
- CWE
- CWE-287
Report tools
Action score
32
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.2%
CNA vs NVD score
- NVD
- 7.8
- CNA · suse
- 9.8
- 2.0 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
| Vendor | Product | CPE |
|---|---|---|
| opensuse | tumbleweed | cpe:2.3:o:opensuse:tumbleweed |
| saltstack | salt | cpe:2.3:a:saltstack:salt |
| suse | suse linux enterprise server | cpe:2.3:o:suse:suse_linux_enterprise_server |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (suse). Independent of NVD's CPE analysis and usually ahead of it.
openSUSE Tumbleweed
- salt and later · up to and including 3002.2-2.1affected
SUSE SUSE Linux Enterprise Server 15 SP 3
- salt and later · before 3002.2-3affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- saltstack saltbefore 3002.2
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.2 | salt | before 3002.2-lp152.3.36.1 | 3002.2-lp152.3.36.1 |
| openSUSE:Leap 15.3 | python-distro | before 1.5.0-3.5.1 | 1.5.0-3.5.1 |
| PyPI | salt | before 3002.2 | 3002.2 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | salt | before 3002.2-37.1 | 3002.2-37.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | salt | before 3002.2-8.41.8.1 | 3002.2-8.41.8.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | python-distro | before 1.5.0-3.5.1 | 1.5.0-3.5.1 |
Same product
opensuse: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-46810A UNIX Symbolic Link (Symlink) Following vulnerability in the packaging of openSUSE Tumbleweed traefik2 allows the traefik user to escalate…34Monitor
- CVE-2023-32183Incorrect Default Permissions vulnerability in the openSUSE Tumbleweed hawk2 package allows users with access to the hacluster to escalate…31Monitor
- CVE-2022-31250keylime %post scriplet allows for privilege escalation from keylime user to root31Monitor
Published before and after this one in the same product
- Later →CVE-2024-49506Nov 13, 2024 · Fixed temporary file path in aeon-checks allows fixing of disk encryption key29Monitor
- Later →CVE-2025-53881Oct 2, 2025 · SUSE-specific logrotate configuration allows escalation from mail user/group to root27Monitor
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 |
|---|---|---|
| opensuse:python-distro | 1.5.0-3.5.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:salt | 3002.2-lp152.3.36.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| PyPI:salt | 3002.2 | Package registry (OSV) |
| suse:python-distro | 1.5.0-3.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2 | Package registry (OSV) |
| suse:salt | 3002.2-8.41.8.1 · SUSE:Linux Enterprise High Performance Computing 15-ESPOS | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
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 (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.