Skip to content
Noroxi
CVE-2013-4437· NVD / CVE Program· CNA redhat

Unspecified vulnerability in salt-ssh in Salt (aka SaltStack) 0.17.0 has unspecified impact and vectors related to "insecure Usage of /tmp."

CriticalCVSS 10.0 · v2.0—No exploit Fix available
Published
Nov 5, 2013
Updated
Jun 16, 2026
EPSS
1.5% · 72th percentile
CWE
—
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
40 / 40 · 10.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.5%

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

Package-level exposure

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

EcosystemPackageAffected rangeFix
PyPIsaltfrom 0.17.0 · before 0.17.10.17.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
  • 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:salt0.17.1Package 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.

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

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
C · data can be read
Integrity
C · data or configuration can be modified
Availability
C · the service can be disrupted
Attack complexity
Low
Confidentiality impact
C
Integrity impact
C
Availability impact
C

Weakness class (CWE)

—

CVSS vector

AV:N/AC:L/Au:N/C:C/I:C/A:C

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; 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

Change log

  1. Fix✗ → ✓

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

References

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

All records