Continued command execution via omitted PAM account check
Published Jun 22, 2022 · Updated May 5, 2025
Incorrect authorization in Salt before 3002.9, 3003.5, or 3004.2 allows remote authenticated users with locked accounts to run commands. The PAM eAuth backend accepts valid credentials without enforcing the PAM account-status result, so locking an account does not revoke its Salt authorization. Reachability requires prior authorization and PAM eAuth through salt-api, or an existing local shell session; commands retain the account's configured Salt permissions.
Summary
What happened
Incorrect authorization in Salt before 3002.9, 3003.5, or 3004.2 allows remote authenticated users with locked accounts to run commands. The PAM eAuth backend accepts valid credentials without enforcing the PAM account-status result, so locking an account does not revoke its Salt authorization. Reachability requires prior authorization and PAM eAuth through salt-api, or an existing local shell session; commands retain the account's configured Salt permissions.
The record
- CVE
- CVE-2022-22967
- Published
- Jun 22, 2022
- Updated
- May 5, 2025
- Vendor
- Salt Project
- Product
- Salt
- Classifications
- CWE-863, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 22, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=SaltStack Salt prior to 3002.9, 3003.5, 3004.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo