# A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name...

Advisory record · `GHSA-h653-95qw-h2mp`

- **Identifiers:** `GHSA-h653-95qw-h2mp` · `CVE-2019-14858` · `PYSEC-2019-171`
- **State:** Confirmed
- **Severity:** CVSS 7.3 High
- **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:** 14 Oct 2019
- **Updated:** 10 Jun 2026
- **Reviewed by a person:** No

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

## Affected packages

- `ansible` (PyPI): affected `>=2.0, <2.8.1`; fixed in `2.8.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Ansible engine versions 2.0 up to 2.8.1 (fixed in 2.8.1) are affected, along with Ansible Tower 3.x up to 3.5. When a module's sub-parameters are marked no_log and an invalid parameter name is passed, the task fails before masking is applied, so sensitive values in those sub-parameters can appear in output at increased verbosity. Upgrade ansible to version 2.8.1 or later. The source gives no workaround.

Written 9 Nov 2026.

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

- 7.3 High, CVSS 3.0: `CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0042, the 37th percentile, on 20 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 14 Oct 2019. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-h653-95qw-h2mp](https://github.com/advisories/GHSA-h653-95qw-h2mp)
- [OSV: GHSA-h653-95qw-h2mp](https://osv.dev/vulnerability/GHSA-h653-95qw-h2mp)
- <https://access.redhat.com/errata/RHSA-2019:3207>
- <https://access.redhat.com/errata/RHSA-2019:3201>
- <https://access.redhat.com/errata/RHSA-2019:3202>
- <https://access.redhat.com/errata/RHSA-2019:3203>
- <https://access.redhat.com/errata/RHSA-2020:0756>
- <http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.html>
- <http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.html>
- <https://github.com/advisories/GHSA-h653-95qw-h2mp>

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-h653-95qw-h2mp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h653-95qw-h2mp/>. Everything for agents: <https://agentprime.io/llms.txt>.
