VYPR
High severityNVD Advisory· Published Jun 22, 2022· Updated May 5, 2025

CVE-2022-22967

CVE-2022-22967

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

SaltStack Salt PAM authentication fails to reject locked accounts, allowing previously authorized users to continue running commands after account lock.

Vulnerability

Overview CVE-2022-22967 is an authentication bypass vulnerability in SaltStack Salt versions prior to 3002.9, 3003.5, and 3004.2 [1]. The issue lies in the PAM (Pluggable Authentication Modules) authentication mechanism, which fails to properly check the account lock status. When a user's account is locked (e.g., due to failed login attempts or administrative action), the PAM auth module still allows that user to execute Salt commands if they have an active session or authenticate via salt-api using PAM eauth [1][2].

Exploitation

An attacker who previously had valid credentials and whose account has been subsequently locked can continue to run Salt commands without re-authentication. This affects both local shell accounts with an existing session and remote salt-api users that authenticate through PAM eauth [1]. The attack requires that the user already had authorized access before the lock, and the account lock is not enforced by the PAM module. No additional privileges are needed beyond the existing session or API token [2].

Impact

Successful exploitation allows a locked-out user to maintain access to Salt's management capabilities, potentially executing arbitrary commands on managed minions, modifying configurations, or exfiltrating data. This undermines account lockout policies and can lead to unauthorized persistent access within the infrastructure [1][2].

Mitigation

The vulnerability is fixed in Salt versions 3002.9, 3003.5, and 3004.2 [1]. Users should upgrade to these or later versions. There is no known workaround; upgrading is the recommended action. The issue is not listed in CISA's Known Exploited Vulnerabilities catalog as of the publication date [2].

AI Insight generated on May 21, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
saltPyPI
< 3002.93002.9
saltPyPI
>= 3003.0, < 3003.53003.5
saltPyPI
>= 3004.0, < 3004.23004.2

Affected products

38

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

8

News mentions

0

No linked articles in our index yet.