NVD / CVE Program· CNA mitre

CVE-2018-15750: 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 dete

Noroxi assessment

Priority: Monitor (action score 22/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.2% (FIRST EPSS); higher than 91% 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 (Debian:9) 2016.11.2+ds-1+deb9u5; salt (openSUSE:Leap 15.1) 3000-lp151.5.21.1; salt (openSUSE:Leap 15.2) 3002.2-lp152.3.36.1.

Low priority for now. Upgrade to salt (Debian:9) 2016.11.2+ds-1+deb9u5; salt (openSUSE:Leap 15.1) 3000-lp151.5.21.1; salt (openSUSE:Leap 15.2) 3002.2-lp152.3.36.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

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 determine which files exist on the server.

MediumCVSS 5.3 · v3.0—No exploit Fix available

Published: Oct 24, 2018
Updated: Jun 16, 2026
EPSS: 4.2% · 91th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 4.2%

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

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.

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
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 records

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-14696Oct 24, 2017 · SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before 2017.7.2 allows remote attackers to cause a denial of servic
31Monitor
← EarlierCVE-2017-7893Apr 23, 2018 · In SaltStack Salt before 2016.3.6, compromised salt-minions can impersonate the salt-master.
39Monitor
Later →CVE-2018-15751Oct 24, 2018 · SaltStack Salt before 2017.7.8 and 2018.3.x before 2018.3.3 allow remote attackers to bypass authentication and execute arbitrary commands v
40Plan

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

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

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.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: low · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: Low
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

nvd-primary

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 class

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

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.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)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:46 PM UTC

For records you follow, these changes also arrive as notifications. →

References

lists.opensuse.org/opensuse-security-announce/2020-07/msg00070.html

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records