Skip to content
Noroxi
CVE-2022-22941· NVD / CVE Program· CNA vmware

An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1.

Noroxi assessment

Priority: Monitor (action score 35/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: salt (openSUSE:Leap 15.3) 3002.2-150300.53.10.1; salt (PyPI) 3003.4, 3004.1, 3002.8; salt (SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS) 3002.2-150100.57.1, 3002.2-150100.63.1.

Low priority for now. Upgrade to salt (openSUSE:Leap 15.3) 3002.2-150300.53.10.1; salt (PyPI) 3003.4, 3004.1, 3002.8; salt (SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS) 3002.2-150100.57.1, 3002.2-150100.63.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 8.8 · v3.1—No exploit Fix available
Published
Mar 29, 2022
Updated
Jun 17, 2026
EPSS
1.3% · 71th percentile

Report tools

JSON

Action score

35

Monitor

Low priority for now.

CVSS
35 / 40 · 8.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-22941

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
saltstacksalt

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • saltstack salt3002 and later · before 3002.8
  • saltstack salt3003 and later · before 3003.4
  • saltstack salt3004 and later · before 3004.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a SaltStack Salt

    • SaltStack Salt prior to 3002.8, 3003.4, 3004.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 15.3saltbefore 3002.2-150300.53.10.13002.2-150300.53.10.1
PyPIsaltfrom 3003 · before 3003.43003.4
PyPIsaltfrom 3004 · before 3004.13004.1
PyPIsaltbefore 3002.83002.8
SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOSsaltbefore 3002.2-150100.57.13002.2-150100.57.1
SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOSsaltbefore 3002.2-150100.63.13002.2-150100.63.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOSsaltbefore 3002.2-150200.58.13002.2-150200.58.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOSsaltbefore 3002.2-150200.64.13002.2-150200.64.1
SUSE:Linux Enterprise High Performance Computing 15-ESPOSsaltbefore 3002.2-150000.8.41.32.13002.2-150000.8.41.32.1
SUSE:Linux Enterprise High Performance Computing 15-ESPOSsaltbefore 3002.2-150000.8.41.26.13002.2-150000.8.41.26.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3saltbefore 3002.2-150300.53.10.13002.2-150300.53.10.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3saltbefore 3002.2-150300.53.16.13002.2-150300.53.16.1
SUSE:Linux Enterprise Module for Basesystem 15 SP3saltbefore 3002.2-150300.53.16.13002.2-150300.53.16.1
SUSE:Manager Client Tools 12saltbefore 3000-58.13000-58.1
SUSE:Manager Client Tools 12saltbefore 3000-62.13000-62.1
SUSE:Manager Client Tools 12venv-salt-minionbefore 3004-3.8.13004-3.8.1
SUSE:Manager Client Tools 15venv-salt-minionbefore 3004-150000.3.8.13004-150000.3.8.1
SUSE:Manager Server 4.1release-notes-susemanagerbefore 4.1.14.1-150200.3.77.14.1.14.1-150200.3.77.1
SUSE:Manager Server 4.2release-notes-susemanagerbefore 4.2.5.1-150300.3.34.14.2.5.1-150300.3.34.1

Other highest-scoring records for the same primary product.

  • CVE-2020-16846An issue was discovered in SaltStack Salt through 3002.KEV
    99Now
  • CVE-2020-11651An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV
    98Now
  • CVE-2020-11652An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV
    82Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-22935Mar 29, 2022 · An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1.
    14Monitor
  • ← EarlierCVE-2022-22936Mar 29, 2022 · An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1.
    35Monitor
  • Later →CVE-2022-22967Jun 23, 2022 · An issue was discovered in SaltStack Salt in versions before 3002.9, 3003.5, 3004.2.
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
opensuse:salt3002.2-150300.53.16.1 · openSUSE:Leap 15.3Package registry (OSV)
PyPI:salt3002.8Package registry (OSV)
PyPI:salt3003.4Package registry (OSV)
PyPI:salt3004.1Package registry (OSV)
suse:release-notes-susemanager4.1.14.1-150200.3.77.1 · SUSE:Manager Server 4.1Package registry (OSV)
suse:salt3000-62.1 · SUSE:Manager Client Tools 12Package registry (OSV)
suse:salt3002.2-150300.53.16.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package registry (OSV)
suse:venv-salt-minion3004-150000.3.8.1 · SUSE:Manager Client Tools 15Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records