Skip to content

SaltStack Salt Improper Validation of eauth credentials and tokens in salt-netapi

Critical severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Oct 22, 2024

Package

pip salt (pip)

Affected versions

< 2015.8.13
>= 2016.3.0, < 2016.3.8
>= 2016.11.0, < 2016.11.10
>= 2017.5.0, < 2017.7.8
>= 2018.2.0, < 2018.3.5
>= 2019.2.0, < 2019.2.7
>= 3000.0, < 3000.5
>= 3001.0, < 3001.3
>= 3002.0, < 3002.1

Patched versions

2015.8.13
2016.3.8
2016.11.10
2017.7.8
2018.3.5
2019.2.7
3000.5
3001.3
3002.1

Description

In SaltStack the salt-netapi improperly validates eauth credentials and tokens. A user can bypass authentication and invoke Salt SSH.

References

Published by the National Vulnerability Database Nov 6, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Apr 22, 2024
Last updated Oct 22, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(97th percentile)

Weaknesses

CVE ID

CVE-2020-25592

GHSA ID

GHSA-29j3-2446-5j4w

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.