Skip to content

SaltStack Salt Permissions Bypass

High severity GitHub Reviewed Published Mar 30, 2022 to the GitHub Advisory Database • Updated Oct 22, 2024

Package

pip salt (pip)

Affected versions

>= 3003, < 3003.4
>= 3004, < 3004.1
< 3002.8

Patched versions

3003.4
3004.1
3002.8

Description

An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. When configured as a Master-of-Masters, with a publisher_acl, if a user configured in the publisher_acl targets any minion connected to the Syndic, the Salt Master incorrectly interpreted no valid targets as valid, allowing configured users to target any of the minions connected to the syndic with their configured commands. This requires a syndic master combined with publisher_acl configured on the Master-of-Masters, allowing users specified in the publisher_acl to bypass permissions, publishing authorized commands to any configured minion.

References

Published by the National Vulnerability Database Mar 29, 2022
Published to the GitHub Advisory Database Mar 30, 2022
Reviewed Apr 22, 2024
Last updated Oct 22, 2024

Severity

High

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
Low
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:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.302%
(70th percentile)

Weaknesses

CVE ID

CVE-2022-22941

GHSA ID

GHSA-qcr3-hr2f-6557

Source code

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