Skip to content

SaltStack Salt command injection in the Salt-API when using the Salt-SSH client

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

Package

pip salt (pip)

Affected versions

< 2015.8.13
>= 2016.3.0, < 2016.11.5
>= 2016.11.7, < 2016.11.10
>= 2017.5.0, < 2017.7.8
>= 2018.2.0, <= 2018.3.5
>= 2019.2.0, < 2019.2.8
>= 3000, < 3000.7
>= 3001, < 3001.5
>= 3002, < 3002.3

Patched versions

2015.8.13
2016.11.5
2016.11.10
2017.7.8
2019.2.8
3000.7
3001.5
3002.3

Description

An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.

References

Published by the National Vulnerability Database Feb 27, 2021
Published to the GitHub Advisory Database May 24, 2022
Reviewed Apr 22, 2024
Last updated Oct 23, 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

5.896%
(94th percentile)

Weaknesses

CVE ID

CVE-2021-3148

GHSA ID

GHSA-ghc2-hx3w-jqmp

Source code

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