Skip to content

GHSA-4j59-vv55-q6h3 CVE-2024-38825 PYSEC-2026-1893

Salt's salt.auth.pki module does not properly authenticate callers

Medium PyPI
Severity
6.4 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.15%
Chance of exploitation in the next 30 days. Higher than 4.46% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
Fix
3006.12
Upgrade salt to this version or later

Description

The salt.auth.pki module does not properly authenticate callers. The "password" field contains a public certificate which is validated against a CA certificate by the module. This is not pki authentication, as the caller does not need access to the corresponding private key for the authentication attempt to be accepted.

Affected versions

PyPI

PackageVulnerableFixed in
salt
>= 3006.0rc1, < 3006.12
3006.12
salt
>= 3007.0rc1, < 3007.4
3007.4
salt
>= 3006.0rc1, < 3006.12
>= 3007.0rc1, < 3007.4
3006.12
3007.4

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

salt PyPI → 3006.12

pip
pip install --upgrade "salt>=3006.12"
poetry
poetry add "salt>=3006.12"
uv
uv add "salt>=3006.12"

Severity breakdown

CVSS 3.1 6.4

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2020-16846
SaltStack Salt Command Injection in netapi ssh client
Critical Known exploited Also affects salt
CVE-2020-11652
SaltStack Salt is vulnerable Arbitrary Directory Access
High Known exploited Also affects salt
CVE-2020-11651
SaltStack Salt Unauthenticated Remote Code Execution
Critical Known exploited Also affects salt
GHSA-vcf3-26xf-fw4m
Salt Authentication Protocol Version Downgrade Allows Minion Impersonation
Medium Also affects salt
GHSA-77w2-v593-vxvv
Salt junos Module Vulnerable to Code Injection via Specially Crafted YAML Payload
High Also affects salt
GHSA-8pcp-r83j-fc92
Salt vulnerable to directory traversal attack in file receiving method
High Also affects salt
GHSA-989c-m532-p2hv
Salt's worker process vulnerable to denial of service through file read operation
Medium Also affects salt
GHSA-7f3f-x5f5-79gw
Salt's file contents overwrite the VirtKey class
Medium Also affects salt
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor