CVE-2022-22936

An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1. Job publishes and file server replies are susceptible to replay attacks, which can result in an attacker replaying job publishes causing minions to run old jobs. File server replies can also be re-played. A sufficient craft attacker could gain root access on minion under certain scenarios.

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-22936 is rated Moderate Risk (43.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.08%). Review affected assets and schedule remediation.

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-22936

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.26% 0.08% -0.18%
2 2025-11-18 0.06% 0.26% +0.20%
3 2025-03-17 — 0.06% —

Full EPSS history (7 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
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:N)
No account or special rights needed—anonymous or random user is enough.
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:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
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:N)
No account or special rights needed—anonymous or random user is enough.
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
5.4 2.0 MEDIUM
AV:A/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 5.5 6.4 [email protected]

Weakness enumeration for CVE-2022-22936

GitHub Security Advisory for CVE-2022-22936

GHSA-5r3f-3m3j-wcj2 · Severity: high · Ecosystem: pip — SaltStack Salt Authentication Bypass by Capture-replay

OS Trackers for CVE-2022-22936

vendor priority summary link
alpine — CVE-2022-22936: 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-22936
gentoo high CVE-2022-22936: 1 GLSA(s) (202310-22), 1 atom(s) (app-admin/salt); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-22936
suse high — https://www.suse.com/security/cve/CVE-2022-22936/
ubuntu medium CVE-2022-22936 medium 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-22936

Affected software / configurations for CVE-2022-22936

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-22936

cvelogic Threat Intelligence