# Ansible Path Traversal vulnerability

Advisory record · `GHSA-74vq-h4q8-x6jv`

- **Identifiers:** `GHSA-74vq-h4q8-x6jv` · `CVE-2019-3828` · `PYSEC-2019-5`
- **State:** Confirmed
- **Severity:** CVSS 4.2 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 15 Apr 2019
- **Updated:** 27 Nov 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 15 Apr 2019, 16:19 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `ansible` (PyPI): affected `<2.5.15 || >=2.6.0a1, <2.6.14 || >=2.7.0a1, <2.7.8`; fixed in `2.5.15`, `2.6.14`, `2.7.8`

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0052, the 45th percentile, on 21 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 15 Apr 2019. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-74vq-h4q8-x6jv](https://github.com/advisories/GHSA-74vq-h4q8-x6jv)
- [OSV: GHSA-74vq-h4q8-x6jv](https://osv.dev/vulnerability/GHSA-74vq-h4q8-x6jv)
- <https://nvd.nist.gov/vuln/detail/CVE-2019-3828>
- <https://github.com/ansible/ansible/pull/52133>
- <https://github.com/ansible/ansible/commit/396a2f74717477d80600450e2b7e45349d7b5110>
- <https://github.com/ansible/ansible/commit/4be3215d2f9f84ca283895879f0c6ce1ed7dd333>
- <https://github.com/ansible/ansible/commit/f3edc091523fbe301926b7a0db25fbbd96940d93>
- <https://access.redhat.com/errata/RHSA-2019:3744>
- <https://access.redhat.com/errata/RHSA-2019:3789>
- <https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3828>
- <https://github.com/advisories/GHSA-74vq-h4q8-x6jv>
- <https://github.com/ansible/ansible>
- <https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2019-5.yaml>
- <https://usn.ubuntu.com/4072-1>

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-74vq-h4q8-x6jv>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-74vq-h4q8-x6jv/>. Everything for agents: <https://agentprime.io/llms.txt>.
