# Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible

Advisory record · `GHSA-77g3-3j5w-64w4`

- **Identifiers:** `GHSA-77g3-3j5w-64w4` · `CVE-2020-10685` · `PYSEC-2020-1`
- **State:** Confirmed
- **Severity:** CVSS 5.0 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-377](https://cwe.mitre.org/data/definitions/377.html) · [CWE-459](https://cwe.mitre.org/data/definitions/459.html) · [CWE-668](https://cwe.mitre.org/data/definitions/668.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-377](https://agentprime.io/advisories/tag/cwe-377.md) · [CWE-459](https://agentprime.io/advisories/tag/cwe-459.md)
- **Published:** 7 Apr 2021
- **Updated:** 6 Sept 2024
- **Reviewed by a person:** No

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

## Affected packages

- `ansible` (PyPI): affected `>=2.7.0a1, <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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0036, the 30th percentile, on 7 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-77g3-3j5w-64w4](https://github.com/advisories/GHSA-77g3-3j5w-64w4)
- [OSV: GHSA-77g3-3j5w-64w4](https://osv.dev/vulnerability/GHSA-77g3-3j5w-64w4)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-10685>
- <https://github.com/ansible/ansible/pull/68433>
- <https://github.com/ansible/ansible/commit/4e1fe80e681fa466626e9dea53efe6b0253ea1b2>
- <https://github.com/ansible/ansible/commit/51d2514753544a9d58cd7524e27e696b2c944fb5>
- <https://github.com/ansible/ansible/commit/e1273b6faf036ed84e4f4edee85b888a4e256aee>
- <https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-10685>
- <https://github.com/advisories/GHSA-77g3-3j5w-64w4>
- <https://github.com/ansible/ansible>
- <https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-1.yaml>
- <https://security.gentoo.org/glsa/202006-11>
- <https://www.debian.org/security/2021/dsa-4950>

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-77g3-3j5w-64w4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-77g3-3j5w-64w4/>. Everything for agents: <https://agentprime.io/llms.txt>.