CVE-2018-15751: SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands…
Noroxi assessment
Priority: Plan (action score 40/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: 4.9% (FIRST EPSS); higher than 92.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: salt (Alpine:v3.8) 2018.3.3-r0; salt (Debian:9) 2016.11.2+ds-1+deb9u5; salt (openSUSE:Leap 15.1) 3000-lp151.5.21.1.
Add it to your regular patch cycle. Upgrade to salt (Alpine:v3.8) 2018.3.3-r0; salt (Debian:9) 2016.11.2+ds-1+deb9u5; salt (openSUSE:Leap 15.1) 3000-lp151.5.21.1 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
SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands via salt-api(netapi).
- Published
- Oct 24, 2018
- Updated
- Jun 16, 2026
- EPSS
- 4.9% · 92th percentile
- CWE
- CWE-287
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.9%
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 |
|---|---|---|
| saltstack | salt | cpe:2.3:a:saltstack:salt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- saltstack saltbefore 2017.7.8
- saltstack salt2018.3.0 and later · before 2018.3.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.8 | salt | from 2018.3.0 · before 2018.3.3-r0 | 2018.3.3-r0 |
| Debian:9 | salt | before 2016.11.2+ds-1+deb9u5 | 2016.11.2+ds-1+deb9u5 |
| openSUSE:Leap 15.1 | salt | before 3000-lp151.5.21.1 | 3000-lp151.5.21.1 |
| 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 | from 2016.11.0 · before 2016.11.10 | 2016.11.10 |
| PyPI | salt | from 2017.7.0 · before 2017.7.8 | 2017.7.8 |
| PyPI | salt | from 2018.3.0 · before 2018.3.3 | 2018.3.3 |
| PyPI | salt | before 2017.7.8 | 2017.7.8 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | salt | before 3002.2-37.1 | 3002.2-37.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | salt | before 2018.3.0-5.20.1 | 2018.3.0-5.20.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP1 | salt | before 3000-6.37.1 | 3000-6.37.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | python-distro | before 1.5.0-3.5.1 | 1.5.0-3.5.1 |
| SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLS | salt | before 2016.11.10-43.38.1 | 2016.11.10-43.38.1 |
| SUSE:Manager Client Tools 12 | salt | before 2018.3.0-46.44.1 | 2018.3.0-46.44.1 |
| SUSE:Manager Server 3.2 | py26-compat-salt | before 2016.11.10-6.15.1 | 2016.11.10-6.15.1 |
Same product
saltstack: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-16846An issue was discovered in SaltStack Salt through 3002.KEV99Now
- CVE-2020-11651An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV98Now
- CVE-2020-11652An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV82Now
Published before and after this one in the same product
- ← EarlierCVE-2017-7893Apr 23, 2018 · In SaltStack Salt before 2016.3.6, compromised salt-minions can impersonate the salt-master.39Monitor
- ← EarlierCVE-2018-15750Oct 24, 2018 · Directory Traversal vulnerability in salt-api in SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allows remote attackers to…22Monitor
- Later →CVE-2019-17361Jan 16, 2020 · In SaltStack Salt through 2019.2.0, the salt-api NET API with the ssh client enabled is vulnerable to command injection.44Plan
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 |
|---|---|---|
| alpine:salt | 2018.3.3-r0 · Alpine:v3.8 | Package registry (OSV) |
| debian:salt | 2016.11.2+ds-1+deb9u5 · Debian:9 | Package registry (OSV) |
| opensuse:python-distro | 1.5.0-3.5.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| opensuse:salt | 3000-lp151.5.21.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| PyPI:salt | 2016.11.10 | Package registry (OSV) |
| PyPI:salt | 2017.7.8 | Package registry (OSV) |
| PyPI:salt | 2018.3.3 | Package registry (OSV) |
| suse:py26-compat-salt | 2016.11.10-6.15.1 · SUSE:Manager Server 3.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 | 2016.11.10-43.38.1 · SUSE:Linux Enterprise Server 11 SP3-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.
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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/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
Show all references (6 more)Show less
- docs.saltstack.com/en/2017.7/topics/releases/2017.7.8.html
- docs.saltstack.com/en/latest/topics/releases/2018.3.3.html
- groups.google.com/d/msg/salt-users/L9xqcJ0UXxs/qgDj42obBQAJ
- groups.google.com/d/msg/salt-users/dimVF7rpphY/jn3Xv3MbBQAJ
- lists.debian.org/debian-lts-announce/2020/07/msg00024.html
- usn.ubuntu.com/4459-1/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.