Skip to content
Noroxi
CVE-2017-14695· NVD / CVE Program· CNA mitre

Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before

Directory traversal vulnerability in minion id validation in SaltStack Salt before 2016.3.8, 2016.11.x before 2016.11.8, and 2017.7.x before 2017.7.2 allows remote minions with incorrect credentials to authenticate to a master via a crafted minion ID. NOTE: this vulnerability exists because of an incomplete fix for CVE-2017-12791.

CriticalCVSS 9.8 · v3.0—No exploit Fix available
Published
Oct 24, 2017
Updated
Jun 16, 2026
EPSS
2.6% · 85th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

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 · 2.6%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
saltstacksalt

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • saltstack saltup to 2016.3.7 inclusive
  • saltstack salt2016.11
  • saltstack salt2016.11.0
  • saltstack salt2016.11.1
  • saltstack salt2016.11.2
  • saltstack salt2016.11.3
  • saltstack salt2016.11.4
  • saltstack salt2016.11.5
  • saltstack salt2016.11.6
  • saltstack salt2016.11.7
  • saltstack salt2017.7.0
  • saltstack salt2017.7.1

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPIsaltfrom 2016.11 · before 2016.11.82016.11.8
PyPIsaltfrom 2016.11.0 · before 2016.11.82016.11.8
PyPIsaltfrom 2017.7 · before 2017.7.22017.7.2
PyPIsaltfrom 2017.7.0 · before 2017.7.22017.7.2
PyPIsaltbefore 2016.3.82016.3.8
SUSE:Linux Enterprise Server 11 SP3-CLIENT-TOOLSsaltbefore 2016.11.4-43.10.22016.11.4-43.10.2
SUSE:Manager Client Tools 12saltbefore 2016.11.4-46.10.12016.11.4-46.10.1
SUSE:Manager Client Tools 12saltbefore 2018.3.0-46.28.12018.3.0-46.28.1
SUSE:Manager Client Tools 12supportutils-plugin-saltbefore 1.1.4-6.9.11.1.4-6.9.1
SUSE:Manager Server 3.1apache-mybatisbefore 3.2.3-1.3.13.2.3-1.3.1
SUSE:Manager Server 3.1hadoopbefore 0.18.1-1.3.10.18.1-1.3.1
SUSE:Manager Server 3.1icu4jbefore 55.1-1.3.155.1-1.3.1
SUSE:Manager Server 3.1lucenebefore 2.4.1-1.3.12.4.1-1.3.1
SUSE:Manager Server 3.1nekohtmlbefore 1.9.21-1.3.11.9.21-1.3.1
SUSE:Manager Server 3.1nutch-corebefore 1.0.1-1.3.11.0.1-1.3.1
SUSE:Manager Server 3.1picocontainerbefore 1.3.7-1.3.11.3.7-1.3.1
SUSE:Manager Server 3.1py26-compat-saltbefore 2016.11.10-1.16.12016.11.10-1.16.1
SUSE:Manager Server 3.1smdbabefore 1.6.2-0.2.9.11.6.2-0.2.9.1
SUSE:Manager Server 3.1spacecmdbefore 2.7.8.13-2.26.12.7.8.13-2.26.1
SUSE:Manager Server 3.1spacewalkbefore 2.7.0.6-2.6.12.7.0.6-2.6.1
SUSE:Manager Server 3.1spacewalk-backendbefore 2.7.73.15-2.26.12.7.73.15-2.26.1
SUSE:Manager Server 3.1spacewalk-brandingbefore 2.7.2.15-2.25.12.7.2.15-2.25.1
SUSE:Manager Server 3.1spacewalk-doc-indexesbefore 2.7.0.4-2.6.12.7.0.4-2.6.1
SUSE:Manager Server 3.1spacewalk-javabefore 2.7.46.17-2.35.12.7.46.17-2.35.1

+11

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
  • CVE-2021-25282An issue was discovered in through SaltStack Salt before 3002.5.
    64This week
  • CVE-2021-3197An issue was discovered in SaltStack Salt before 3002.5.
    61This week
  • CVE-2021-25281An issue was discovered in through SaltStack Salt before 3002.5.
    61This week

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
PyPI:salt2016.11.8Package registry (OSV)
PyPI:salt2016.3.8Package registry (OSV)
PyPI:salt2017.7.2Package registry (OSV)
suse:apache-mybatis3.2.3-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:hadoop0.18.1-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:icu4j55.1-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:lucene2.4.1-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:nekohtml1.9.21-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:nutch-core1.0.1-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:picocontainer1.3.7-1.3.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:py26-compat-salt2016.11.10-1.16.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:salt2016.11.4-46.10.1 · SUSE:Manager Client Tools 12Package registry (OSV)
suse:smdba1.6.2-0.2.9.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:spacecmd2.7.8.13-2.26.1 · SUSE:Manager Server 3.1Package registry (OSV)
suse:supportutils-plugin-salt1.1.4-6.9.1 · SUSE:Manager Client Tools 12Package 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.

EPSS, last 120 days

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.

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

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.

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

Vulnerable

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

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

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

References

All records