CVE-2022-22941

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.

Published: 2022-03-29 Last update: 2025-05-05 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-22941 is rated Low Risk (35.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-22941

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.32% 0.01% -0.30%
2 2025-11-18 0.01% 0.32% +0.31%
3 2025-03-30 — 0.01% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-22941

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
6.0 2.0 MEDIUM
AV:N/AC:M/Au:S/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 6.8 6.4 [email protected]

Weakness enumeration for CVE-2022-22941

GitHub Security Advisory for CVE-2022-22941

GHSA-qcr3-hr2f-6557 · Severity: high · Ecosystem: pip — SaltStack Salt Permissions Bypass

OS Trackers for CVE-2022-22941

vendor priority summary link
alpine — CVE-2022-22941: 1 source package rows (salt); 11 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 7, open 4. https://security.alpinelinux.org/vuln/CVE-2022-22941
gentoo high CVE-2022-22941: 1 GLSA(s) (202310-22), 1 atom(s) (app-admin/salt); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-22941
suse high — https://www.suse.com/security/cve/CVE-2022-22941/
ubuntu low CVE-2022-22941 low priority: Ubuntu including 1 source packages (salt), 13 status rows across 13 suites (bionic, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 6, ignored 5, not-affected 1, released 1. https://ubuntu.com/security/CVE-2022-22941

Affected software / configurations for CVE-2022-22941

Vendor Product Version Raw CPE
saltstack salt >= 3002, < 3002.8 cpe:2.3:a:saltstack:salt:*:*:*:*:*:*:*:*
saltstack salt >= 3003, < 3003.4 cpe:2.3:a:saltstack:salt:*:*:*:*:*:*:*:*
saltstack salt >= 3004, < 3004.1 cpe:2.3:a:saltstack:salt:*:*:*:*:*:*:*:*

References for CVE-2022-22941

cvelogic Threat Intelligence