# CVE-2021-20228: Ansible Exposes Sensitive Information

> Ansible Engine fails to mask sensitive information in sub-options, allowing attackers to read confidential data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2021
- **Updated:** 3 Aug 2024
- **Also known as:** AZL-6304, DEBIAN-CVE-2021-20228, GHSA-5rrg-rr89-x9mv, PYSEC-2021-1, UBUNTU-CVE-2021-20228

## What is CVE-2021-20228?

CVE-2021-20228 is a high-severity vulnerability in Debian Debian Linux, published on 29 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protected by the no_log feature when using the sub-option feature of the basic.py module. This flaw allows an attacker to obtain sensitive information. The highest threat from this vulnerability is to confidentiality.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ansible` | PyPI | All versions | 2.8.19rc1 |
| `ansible` | PyPI | All versions | 2.8.19rc1 |
| `ansible` | PyPI | All versions | 2.9.19 |
| `ansible` | PyPI | From 2.10.0a1 | 2.10.6rc1 |
| `ansible` | PyPI | From 2.10.0a1 | 2.10.6rc1 |
| `ansible` | PyPI | From 2.9.0a1 | 2.9.18rc1 |
| `ansible` | PyPI | From 2.9.0a1 | 2.9.18rc1 |

Products: Debian Debian Linux, Redhat Ansible Automation Platform, Redhat Ansible Engine, Redhat Ansible Tower.

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

Upgrade ansible to a fixed version for your release line: 2.8.19rc1, 2.9.19, 2.10.6rc1 or 2.9.18rc1.

## Is CVE-2021-20228 being exploited?

There is no known exploitation of CVE-2021-20228 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-2021-20228 and fix it if it is affected.

What it is: CVE-2021-20228 is a high-severity vulnerability in Debian Debian Linux, published on 29 Apr 2021. 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-2021-20228 in the wild and no public exploit code.

Affected packages and fixed versions:
- ansible (PyPI): affected all versions; fixed in 2.8.19rc1
- ansible (PyPI): affected all versions; fixed in 2.8.19rc1
- ansible (PyPI): affected all versions; fixed in 2.9.19
- ansible (PyPI): affected from 2.10.0a1; fixed in 2.10.6rc1
- ansible (PyPI): affected from 2.10.0a1; fixed in 2.10.6rc1
- ansible (PyPI): affected from 2.9.0a1; fixed in 2.9.18rc1
- ansible (PyPI): affected from 2.9.0a1; fixed in 2.9.18rc1

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

## Sources

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

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