# Exposure of Sensitive Information to an Unauthorized Actor and Insecure Temporary File in Ansible

Advisory record · `GHSA-vcg8-98q8-g7mj`

- **Identifiers:** `GHSA-vcg8-98q8-g7mj` · `CVE-2020-1740` · `PYSEC-2020-12`
- **State:** Confirmed
- **Severity:** CVSS 3.9 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-377](https://cwe.mitre.org/data/definitions/377.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-377](https://agentprime.io/advisories/tag/cwe-377.md)
- **Published:** 7 Apr 2021
- **Updated:** 4 Sept 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 7 Apr 2021, 21:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ansible` (PyPI): affected `<2.7.17 || >=2.8.0a1, <2.8.11 || >=2.9.0a1, <2.9.7`; fixed in `2.7.17`, `2.8.11`, `2.9.7`

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

- 3.9 Low, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0036, the 29th percentile, on 6 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 7 Apr 2021. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-vcg8-98q8-g7mj](https://github.com/advisories/GHSA-vcg8-98q8-g7mj)
- [OSV: GHSA-vcg8-98q8-g7mj](https://osv.dev/vulnerability/GHSA-vcg8-98q8-g7mj)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-1740>
- <https://github.com/ansible/ansible/issues/67798>
- <https://github.com/ansible/ansible/commit/28f9fbdb5e281976e33f443193047068afb97a9b>
- <https://github.com/ansible/ansible/commit/2a563514f070a0a8ba64aebf6bce21194be96c73>
- <https://github.com/ansible/ansible/commit/685a4b6d3ff72186d2b4ffce73172a5446a71ccc>
- <https://github.com/ansible/ansible/commit/ef32a5bf96a89107986375516285253c1380d7ef>
- <https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1740>
- <https://github.com/advisories/GHSA-vcg8-98q8-g7mj>
- <https://github.com/ansible/ansible>
- <https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-12.yaml>
- <https://lists.debian.org/debian-lts-announce/2020/05/msg00005.html>
- <https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DKPA4KC3OJSUFASUYMG66HKJE7ADNGFW>

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-vcg8-98q8-g7mj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-vcg8-98q8-g7mj/>. Everything for agents: <https://agentprime.io/llms.txt>.