# CVE-2020-14332: Insertion of Sensitive Information into Log File and Improper Output Neutralization for Logs in ansible

> Ansible Engine fails to neutralize sensitive data in check mode events, allowing unauthorized users to read confidential information.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** ALPINE-CVE-2020-14332, DEBIAN-CVE-2020-14332, GHSA-j667-c2hm-f2wp, PYSEC-2020-4, UBUNTU-CVE-2020-14332

## What is CVE-2020-14332?

CVE-2020-14332 is a medium-severity vulnerability in Debian Debian Linux, published on 11 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2020-14332?

7 open source packages ship an affected version, including ansible. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ansible` | PyPI | All versions | 2.8.14 |
| `ansible` | PyPI | All versions | 2.8.14 |
| `ansible` | PyPI | From 2.10.0a1 | 2.10.1rc2 |
| `ansible` | PyPI | From 2.10.0a1 | 2.10.1rc2 |
| `ansible` | PyPI | From 2.8.0 | 2.8.14, 2.9.12 |
| `ansible` | PyPI | From 2.9.0a1 | 2.9.12 |
| `ansible` | PyPI | From 2.9.0a1 | 2.9.12 |

Products: Debian Debian Linux, Redhat Ansible Engine.

## How do I fix CVE-2020-14332?

Upgrade ansible to a fixed version for your release line: 2.8.14, 2.10.1rc2 or 2.9.12.

## Is CVE-2020-14332 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14332 and fix it if it is affected.

What it is: CVE-2020-14332 is a medium-severity vulnerability in Debian Debian Linux, published on 11 Sep 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14332 in the wild and no public exploit code.

Affected packages and fixed versions:
- ansible (PyPI): affected all versions; fixed in 2.8.14
- ansible (PyPI): affected all versions; fixed in 2.8.14
- ansible (PyPI): affected from 2.10.0a1; fixed in 2.10.1rc2
- ansible (PyPI): affected from 2.10.0a1; fixed in 2.10.1rc2
- ansible (PyPI): affected from 2.8.0; fixed in 2.8.14, 2.9.12
- ansible (PyPI): affected from 2.9.0a1; fixed in 2.9.12
- ansible (PyPI): affected from 2.9.0a1; fixed in 2.9.12

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-2020-14332/ (Markdown: https://insights.sbomify.com/CVE-2020-14332/index.md)
```

## Sources

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

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