# CVE-2015-6941: salt password information leaked in debug logs

> Attackers with access to debug logs can read leaked password information from Salt's useradd, cloud, and Linode drivers.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Aug 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cxm4-7qcw-267r, PYSEC-2017-71, UBUNTU-CVE-2015-6941

## What is CVE-2015-6941?

CVE-2015-6941 is a critical vulnerability in n/a, published on 9 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-534 (DEPRECATED: Information Exposure Through Debug Log Files)

## Which versions are affected by CVE-2015-6941?

5 open source packages ship an affected version, including salt. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `salt` | PyPI | From 2015.5 | 2015.5.6, 2015.8.1 |
| `salt` | PyPI | From 2015.5 | 2015.5.6 |
| `salt` | PyPI | From 2015.5 | 2015.5.6 |
| `salt` | PyPI | From 2015.8 | 2015.8.1 |
| `salt` | PyPI | From 2015.8 | 2015.8.1 |

Products: Saltstack Salt 2015.

## How do I fix CVE-2015-6941?

Upgrade salt to a fixed version for your release line: 2015.5.6 or 2015.8.1.

## Is CVE-2015-6941 being exploited?

There is no known exploitation of CVE-2015-6941 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-6918](https://insights.sbomify.com/CVE-2015-6918/): salt leaks git usernames and passwords to the log (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6941 and fix it if it is affected.

What it is: CVE-2015-6941 is a critical vulnerability in n/a, published on 9 Aug 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6941 in the wild and no public exploit code.

Affected packages and fixed versions:
- salt (PyPI): affected from 2015.5; fixed in 2015.5.6, 2015.8.1
- salt (PyPI): affected from 2015.5; fixed in 2015.5.6
- salt (PyPI): affected from 2015.5; fixed in 2015.5.6
- salt (PyPI): affected from 2015.8; fixed in 2015.8.1
- salt (PyPI): affected from 2015.8; fixed in 2015.8.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-6941/ (Markdown: https://insights.sbomify.com/CVE-2015-6941/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-6941
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-6941
- OSV: https://osv.dev/vulnerability/CVE-2015-6941

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-6941/
Summaries are generated and may contain mistakes; the official description above is the record.