GHSA-cxm4-7qcw-267r CVE-2015-6941 PYSEC-2017-71
salt password information leaked in debug logs
- Severity
- 9.8 / 10
- Critical · CVSS 3.0
- Exploit chance (EPSS)
- 2.83%
- Chance of exploitation in the next 30 days. Higher than 86.62% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
2015.5.6- Upgrade salt to this version or later
Description
win_useradd, salt-cloud and the Linode driver in salt 2015.5.x before 2015.5.6, and 2015.8.x before 2015.8.1 leak password information in debug logs.
Affected versions
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| salt | >= 2015.5, < 2015.5.6 |
2015.5.6 |
| salt | >= 2015.8, < 2015.8.1 |
2015.8.1 |
| salt | >= 2015.5, < 2015.5.6>= 2015.8, < 2015.8.1 |
2015.5.62015.8.1 |
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 → 2015.5.6
- pip
pip install --upgrade "salt>=2015.5.6"- poetry
poetry add "salt>=2015.5.6"- uv
uv add "salt>=2015.5.6"
Severity breakdown
CVSS 3.0 9.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Weakness
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
- github.com/saltstack/salt/commit/c0689e32154c41f59840ae10ffc5fbfa30618710
- github.com/saltstack/salt/commit/fdd35374562658f4a20767a3703fab93d92f9ca9
- github.com/twangboy/salt/commit/c0689e32154c41f59840ae10ffc5fbfa30618710
- bugzilla.redhat.com/show_bug.cgi
- docs.saltstack.com/en/latest/topics/releases/2015.5.6.html
- docs.saltstack.com/en/latest/topics/releases/2015.8.1.html
- github.com/pypa/advisory-database/tree/main/vulns/salt/PYSEC-2017-71.yaml
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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