An issue was discovered in SaltStack Salt in versions before 3002.9, 3003.5, 3004.2.
Noroxi assessment
Priority: Monitor (action score 36/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: 2% (FIRST EPSS); higher than 81.2% 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) 3004-150300.53.24.1; salt (openSUSE:Leap 15.4) 3004-150400.8.8.1; salt (PyPI) 3003.5, 3004.2, 3002.9.
Low priority for now. Upgrade to salt (openSUSE:Leap 15.3) 3004-150300.53.24.1; salt (openSUSE:Leap 15.4) 3004-150400.8.8.1; salt (PyPI) 3003.5, 3004.2, 3002.9 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.9, 3003.5, 3004.2. PAM auth fails to reject locked accounts, which allows a previously authorized user whose account is locked still run Salt commands when their account is locked. This affects both local shell accounts with an active session and salt-api users that authenticate via PAM eauth.
- Published
- Jun 23, 2022
- Updated
- Jun 17, 2026
- EPSS
- 2.0% · 81th percentile
- CWE
- CWE-863
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.0%
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| saltstack | salt | cpe:2.3:a:saltstack:salt |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- saltstack saltbefore 3002.9
- saltstack salt3003 and later · before 3003.5
- saltstack salt3004 and later · before 3004.2
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.9, 3003.5, 3004.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.3 | salt | before 3004-150300.53.24.1 | 3004-150300.53.24.1 |
| openSUSE:Leap 15.4 | salt | before 3004-150400.8.8.1 | 3004-150400.8.8.1 |
| PyPI | salt | from 3003.0 · before 3003.5 | 3003.5 |
| PyPI | salt | from 3004.0 · before 3004.2 | 3004.2 |
| PyPI | salt | before 3002.9 | 3002.9 |
| SUSE:Linux Enterprise High Performance Computing 15 SP1-ESPOS | salt | before 3004-150100.71.1 | 3004-150100.71.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP2-ESPOS | salt | before 3004-150200.72.1 | 3004-150200.72.1 |
| SUSE:Linux Enterprise High Performance Computing 15-ESPOS | salt | before 3004-150000.8.41.40.1 | 3004-150000.8.41.40.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP3 | salt | before 3004-150300.53.24.1 | 3004-150300.53.24.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP4 | salt | before 3004-150400.8.8.1 | 3004-150400.8.8.1 |
| SUSE:Manager Client Tools 12 | salt | before 3000-65.1 | 3000-65.1 |
| SUSE:Manager Client Tools 12 | venv-salt-minion | before 3004-3.11.1 | 3004-3.11.1 |
| SUSE:Manager Client Tools 15 | venv-salt-minion | before 3004-150000.3.11.1 | 3004-150000.3.11.1 |
Same product
saltstack: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-16846An issue was discovered in SaltStack Salt through 3002.KEV99Now
- CVE-2020-11651An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV98Now
- CVE-2020-11652An issue was discovered in SaltStack Salt before 2019.2.4 and 3000 before 3000.2.KEV82Now
Published before and after this one in the same product
- ← EarlierCVE-2022-22936Mar 29, 2022 · An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1.35Monitor
- ← EarlierCVE-2022-22941Mar 29, 2022 · An issue was discovered in SaltStack Salt in versions before 3002.8, 3003.4, 3004.1.35Monitor
- Later →CVE-2021-33226Feb 17, 2023 · Buffer Overflow vulnerability in Saltstack v.3003 and before allows attacker to execute arbitrary code via the func variable in salt/salt/mo39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:salt | 3004-150300.53.24.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| PyPI:salt | 3002.9 | Package registry (OSV) |
| PyPI:salt | 3003.5 | Package registry (OSV) |
| PyPI:salt | 3004.2 | Package registry (OSV) |
| suse:salt | 3000-65.1 · SUSE:Manager Client Tools 12 | Package registry (OSV) |
| suse:salt | 3004-150300.53.24.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3 | Package registry (OSV) |
| suse:venv-salt-minion | 3004-150000.3.11.1 · SUSE:Manager Client Tools 15 | Package 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.
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.
Credits
All researchersFinders, 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
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.