Skip to content

GHSA-mfr3-9cj8-h2qm CVE-2014-3563 PYSEC-2014-18

SaltStack Salt Insecure Temporary File Creation

High PyPI
Severity
High
The publisher's own rating, not a CVSS score
Exploit chance (EPSS)
0.41%
Chance of exploitation in the next 30 days. Higher than 35.02% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-59 Improper Link Resolution Before File Access ('Link Following')
Fix
2014.1.10
Upgrade salt to this version or later

Description

Multiple unspecified vulnerabilities in Salt (aka SaltStack) before 2014.1.10 allow local users to have an unspecified impact via vectors related to temporary file creation in (1) seed.py, (2) salt-ssh, or (3) salt-cloud.

Affected versions

PyPI

PackageVulnerableFixed in
salt
< 2014.1.10
2014.1.10

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

salt PyPI → 2014.1.10

pip
pip install --upgrade "salt>=2014.1.10"
poetry
poetry add "salt>=2014.1.10"
uv
uv add "salt>=2014.1.10"

Weakness

CWE-59: Improper Link Resolution Before File Access ('Link Following')

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

How to prevent it
  • Architecture and Design: Follow the principle of least privilege when assigning access rights to entities in a software system. Denying access to a file can prevent an attacker from replacing that file with a link to a sensitive file. Ensure good compartmentalization in the system to provide protected areas that can be trusted.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2020-16846
SaltStack Salt Command Injection in netapi ssh client
Critical Known exploited Also affects salt
CVE-2020-11652
SaltStack Salt is vulnerable Arbitrary Directory Access
High Known exploited Also affects salt
CVE-2020-11651
SaltStack Salt Unauthenticated Remote Code Execution
Critical Known exploited Also affects salt
GHSA-vcf3-26xf-fw4m
Salt Authentication Protocol Version Downgrade Allows Minion Impersonation
Medium Also affects salt
GHSA-77w2-v593-vxvv
Salt junos Module Vulnerable to Code Injection via Specially Crafted YAML Payload
High Also affects salt
GHSA-8pcp-r83j-fc92
Salt vulnerable to directory traversal attack in file receiving method
High Also affects salt
GHSA-989c-m532-p2hv
Salt's worker process vulnerable to denial of service through file read operation
Medium Also affects salt
GHSA-7f3f-x5f5-79gw
Salt's file contents overwrite the VirtKey class
Medium Also affects salt
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor