CVE-2022-22936
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a replay attack vulnerability in SaltStack Salt's communication protocol. An attacker can capture and replay valid job publishes or file server replies, causing minions to execute previously-run jobs or serve stale file content. Under certain conditions, this can allow an attacker to gain root access on minions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3002, < 3002.8>= 3003, < 3003.4>= 3004, < 3004.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Salt master versionRun 'salt-master --version' or 'salt --version' on the master nodeAffected if Version is >= 3002 and < 3002.8, or >= 3003 and < 3003.4, or >= 3004 and < 3004.1
-
Check Salt minion versionRun 'salt-minion --version' on each minion node, or use 'salt "*" cmd.run "salt-minion --version"' from the masterAffected if Version is >= 3002 and < 3002.8, or >= 3003 and < 3003.4, or >= 3004 and < 3004.1
-
Identify all Salt installations on the networkInventory all systems running salt-master or salt-minion services using 'ps aux | grep salt' or checking package managersAffected if Any system runs a Salt version in the affected ranges
-
Review Salt job history for anomaliesExamine /var/log/salt/master or use 'salt-run jobs.list_jobs' to look for duplicate job IDs or unexpected repeated executionsAffected if Duplicate job IDs or jobs re-executing unexpectedly are found in logs
You are affected if any Salt master or minion in your environment runs a version within 3002.x before 3002.8, 3003.x before 3003.4, or 3004.x before 3004.1.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3002.83003.43004.1
Upgrade Salt to version 3002.8, 3003.4, 3004.1 or later, which includes replay attack protection mechanisms. Additionally, implement network-level controls to prevent unauthorized capture of Salt traffic.
3002.8, 3003.4, or 3004.1 (depending on your current version branch)
- Identify your current Salt version using `salt --version` or `salt-master --version`
- If running >= 3002 and < 3002.8, upgrade to version 3002.8
- If running >= 3003 and < 3003.4, upgrade to version 3003.4
- If running >= 3004 and < 3004.1, upgrade to version 3004.1
- Upgrade method depends on installation method: for example, using pip: `pip install --upgrade salt==<fixed_version>`
- Alternatively, use OS package manager (e.g., apt, yum) with SaltStack repository
- After upgrade, restart salt-master and salt-minion services: `systemctl restart salt-master salt-minion`
- Verify the upgrade was successful by checking the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data