# CVE-2021-20180: Insertion of Sensitive Information into Log File in ansible

> An attacker can steal Bitbucket pipeline credentials from console logs due to insecure logging in the Ansible module.

- **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:** 16 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2021-20180, GHSA-fh5v-5f35-2rv2, PYSEC-2026-618, UBUNTU-CVE-2021-20180

## What is CVE-2021-20180?

CVE-2021-20180 is a medium-severity vulnerability in Ansible, published on 16 Mar 2022. 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 ansible module where credentials are disclosed in the console log by default and not protected by the security feature when using the bitbucket_pipeline_variable module. This flaw allows an attacker to steal bitbucket_pipeline credentials. The highest threat from this vulnerability is to confidentiality.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2021-20180?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ansible` | PyPI | From 2.8.0a1 | 2.8.19, 2.9.18 |
| `ansible` | PyPI | From 2.8.0a1 | 2.8.19 |
| `ansible` | PyPI | From 2.8.0a1 | 2.8.19 |
| `ansible` | PyPI | From 2.9.0b1 | 2.9.18 |
| `ansible` | PyPI | From 2.9.0b1 | 2.9.18 |

Products: Redhat Ansible.

## How do I fix CVE-2021-20180?

Upgrade ansible to a fixed version for your release line: 2.8.19 or 2.9.18.

## Is CVE-2021-20180 being exploited?

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

## Other vulnerabilities in Ansible

- [CVE-2014-4657](https://insights.sbomify.com/CVE-2014-4657/): Ansible Remote Code Execution (critical 9.8)
- [CVE-2014-4966](https://insights.sbomify.com/CVE-2014-4966/): Ansible Arbitrary Code Execution (critical 9.8)
- [CVE-2014-4967](https://insights.sbomify.com/CVE-2014-4967/): Ansible Arbitrary Code Execution (critical 9.8)
- [CVE-2017-7550](https://insights.sbomify.com/CVE-2017-7550/): Ansible Insertion of Sensitive Information into Log File vulnerability (critical 9.8)
- [CVE-2014-3498](https://insights.sbomify.com/CVE-2014-3498/): Ansible Arbitrary Code Execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-20180 and fix it if it is affected.

What it is: CVE-2021-20180 is a medium-severity vulnerability in Ansible, published on 16 Mar 2022. 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-2021-20180 in the wild and no public exploit code.

Affected packages and fixed versions:
- ansible (PyPI): affected from 2.8.0a1; fixed in 2.8.19, 2.9.18
- ansible (PyPI): affected from 2.8.0a1; fixed in 2.8.19
- ansible (PyPI): affected from 2.8.0a1; fixed in 2.8.19
- ansible (PyPI): affected from 2.9.0b1; fixed in 2.9.18
- ansible (PyPI): affected from 2.9.0b1; fixed in 2.9.18

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

## Sources

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

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