BREW-ANSIBLE@10-CVE-2019-14864 (GHSA-3M93-M4Q6-MC6V)
Vulnerability from osv_homebrew – Published: 2026-08-13 16:35 – Updated: 2026-09-09 23:41 – Source websiteAnsible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.
{
"affected": [
{
"ecosystem_specific": {
"fix": "bump",
"range_state": "fixed",
"upstream_fixed_in": "2.9.1"
},
"package": {
"ecosystem": "Homebrew",
"name": "ansible@10",
"purl": "pkg:brew/ansible%4010"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "10.7.0_6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"confidence": "high",
"source": "matched",
"strategy": "registry",
"upstream_evidence": [
{
"ecosystem": "PyPI",
"key": "pkg:pypi/ansible@10.7.0",
"name": "ansible",
"strategy": "registry",
"subject_version": "10.7.0"
},
{
"ecosystem": "Debian",
"key": "Debian/ansible",
"name": "ansible",
"strategy": "distro"
},
{
"ecosystem": "PyPI",
"key": "upstream:pkg:pypi/ansible@10.7.0",
"name": "ansible",
"strategy": "distro",
"subject_version": "10.7.0"
}
]
},
"details": "Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.",
"id": "BREW-ansible@10-CVE-2019-14864",
"modified": "2026-09-09T23:41:05Z",
"published": "2026-08-13T16:35:22Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-14864"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/issues/63522"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/pull/63527"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/pull/64273"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/pull/64274"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/pull/64748"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/commit/050f92f96054bf59e283fdec9972323c2ed00348"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/commit/75288a89d0053d6df35c90863fb6c9542d89850e"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/commit/a0ec2976b2716cdecdd7a8f416d96406acd79b7c"
},
{
"type": "WEB",
"url": "https://github.com/ansible/ansible/commit/c76e074e4c71c7621a1ca8159261c1959b5287af"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-14864"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-3m93-m4q6-mc6v"
},
{
"type": "PACKAGE",
"url": "https://github.com/ansible/ansible"
},
{
"type": "WEB",
"url": "https://github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-160.yaml"
},
{
"type": "WEB",
"url": "https://www.debian.org/security/2021/dsa-4950"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00021.html"
},
{
"type": "WEB",
"url": "http://lists.opensuse.org/opensuse-security-announce/2020-04/msg00026.html"
}
],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible",
"upstream": [
"GHSA-3m93-m4q6-mc6v",
"CVE-2019-14864",
"PYSEC-2020-160"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.