Skip to content
Noroxi
NVD / CVE Program· CNA mitre

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…

CriticalCVSS 9.8 · v3.0—No exploit Fix available

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

Report tools

JSON

Action score

40

Plan

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.

Follow CVE-2018-15751

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
saltstacksalt

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.

EcosystemPackageAffected rangeFix
Alpine:v3.8saltfrom 2018.3.0 · before 2018.3.3-r02018.3.3-r0
Debian:9saltbefore 2016.11.2+ds-1+deb9u52016.11.2+ds-1+deb9u5
openSUSE:Leap 15.1saltbefore 3000-lp151.5.21.13000-lp151.5.21.1
openSUSE:Leap 15.2saltbefore 3002.2-lp152.3.36.13002.2-lp152.3.36.1
openSUSE:Leap 15.3python-distrobefore 1.5.0-3.5.11.5.0-3.5.1
PyPIsaltfrom 2016.11.0 · before 2016.11.102016.11.10
PyPIsaltfrom 2017.7.0 · before 2017.7.82017.7.8
PyPIsaltfrom 2018.3.0 · before 2018.3.32018.3.3
PyPIsaltbefore 2017.7.82017.7.8
SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOSsaltbefore 3002.2-37.13002.2-37.1
SUSE:Linux Enterprise Module for Basesystem 15saltbefore 2018.3.0-5.20.12018.3.0-5.20.1
SUSE:Linux Enterprise Module for Basesystem 15 SP1saltbefore 3000-6.37.13000-6.37.1
SUSE:Linux Enterprise Module for Basesystem 15 SP2python-distrobefore 1.5.0-3.5.11.5.0-3.5.1
SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLSsaltbefore 2016.11.10-43.38.12016.11.10-43.38.1
SUSE:Manager Client Tools 12saltbefore 2018.3.0-46.44.12018.3.0-46.44.1
SUSE:Manager Server 3.2py26-compat-saltbefore 2016.11.10-6.15.12016.11.10-6.15.1

Other highest-scoring records for the same primary product.

  • CVE-2020-16846An issue was discovered in SaltStack Salt through 3002.KEV
    99Now
  • CVE-2020-11651An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV
    98Now
  • CVE-2020-11652An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV
    82Now

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 / packageFixed versionSource
alpine:salt2018.3.3-r0 · Alpine:v3.8Package registry (OSV)
debian:salt2016.11.2+ds-1+deb9u5 · Debian:9Package registry (OSV)
opensuse:python-distro1.5.0-3.5.1 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:salt3000-lp151.5.21.1 · openSUSE:Leap 15.1Package registry (OSV)
PyPI:salt2016.11.10Package registry (OSV)
PyPI:salt2017.7.8Package registry (OSV)
PyPI:salt2018.3.3Package registry (OSV)
suse:py26-compat-salt2016.11.10-6.15.1 · SUSE:Manager Server 3.2Package registry (OSV)
suse:python-distro1.5.0-3.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP2Package registry (OSV)
suse:salt2016.11.10-43.38.1 · SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLSPackage 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

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

References

All records