# Insertion of Sensitive Information into Log File and Improper Output Neutralization for Logs in ansible

Advisory record · `GHSA-j667-c2hm-f2wp`

- **Identifiers:** `GHSA-j667-c2hm-f2wp` · `CVE-2020-14332` · `PYSEC-2020-4`
- **State:** Confirmed
- **Severity:** CVSS 5.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-117](https://cwe.mitre.org/data/definitions/117.html) · [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Other injection](https://agentprime.io/advisories/tag/injection.md) · [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 9 Feb 2022
- **Updated:** 5 Sept 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Feb 2022, 21:59 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ansible` (PyPI): affected `<2.8.14 || >=2.9.0a1, <2.9.12 || >=2.10.0a1, <2.10.1rc2`; fixed in `2.8.14`, `2.9.12`, `2.10.1rc2`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.5 Medium, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0041, the 35th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 9 Feb 2022. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-j667-c2hm-f2wp](https://github.com/advisories/GHSA-j667-c2hm-f2wp)
- [OSV: GHSA-j667-c2hm-f2wp](https://osv.dev/vulnerability/GHSA-j667-c2hm-f2wp)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-14332>
- <https://github.com/ansible/ansible/pull/71033>
- <https://github.com/ansible/ansible/commit/291f94934c8c49eef85e6539087f2dfcd001fe4f>
- <https://github.com/ansible/ansible/commit/6cae9a4b168df776bf82deb04b2c62e00c38b49a>
- <https://github.com/ansible/ansible/commit/714cd2ad2eff7f003d728414afcb91591fad5d9a>
- <https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-14332>
- <https://github.com/advisories/GHSA-j667-c2hm-f2wp>
- <https://github.com/ansible/ansible>
- <https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst#security-fixes-3>
- <https://github.com/ansible/ansible/blob/stable-2.8/changelogs/CHANGELOG-v2.8.rst#security-fixes-4>
- <https://github.com/ansible/ansible/blob/stable-2.9/changelogs/CHANGELOG-v2.9.rst#security-fixes-6>
- <https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-4.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-j667-c2hm-f2wp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-j667-c2hm-f2wp/>. Everything for agents: <https://agentprime.io/llms.txt>.
