GHSA-3m93-m4q6-mc6v CVE-2019-14864 PYSEC-2020-160

Inclusion of Sensitive Information in Log Files and Improper Output Neutralization for Logs in Ansible

Medium PyPI

Severity: 6.5 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 1.87%; Chance of exploitation in the next 30 days. Higher than 79.38% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-532 Insertion of Sensitive Information into Log File
Fix: 2.7.15; Upgrade ansible to this version or later

Description

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.

Affected versions

PyPI

Package	Vulnerable	Fixed in
ansible	`>= 2.7.0a1, < 2.7.15`	`2.7.15`
ansible	`>= 2.8.0a1, < 2.8.7`	`2.8.7`
ansible	`>= 2.9.0a1, < 2.9.1`	`2.9.1`
ansible	`>= 2.7.0, < 2.7.15` `>= 2.8.0, < 2.8.7` `>= 2.9.0, < 2.9.1`	`2.7.15` `2.8.7` `2.9.1`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

ansible PyPI → `2.7.15`

pip

pip install --upgrade "ansible>=2.7.15"

poetry

poetry add "ansible>=2.7.15"

uv

uv add "ansible>=2.7.15"

Severity breakdown

CVSS 3.1 6.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Weakness

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it

Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution: Remove debug log files before deploying the application into production.
Operation: Protect log files against unauthorized read/write.
Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Advisories

Packages

github.com/ansible/ansible

Timeline

Jan 2, 2020 Published
Sep 4, 2024 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-8ggh-xwr9-3373 Ansible Community General Collection is vulnerable to exposure of sensitive information	Medium	Also affects ansible
GHSA-jpvw-p8pr-9g2x Ansible symlink attack vulnerability	Medium	Also affects ansible
GHSA-cpx3-93w7-457x Ansible leaks password to logs	High	Also affects ansible
GHSA-fh5v-5f35-2rv2 Insertion of Sensitive Information into Log File in ansible	Medium	Also affects ansible
GHSA-4r65-35qq-ch8j Ansible discloses sensitive information in traceback error message	Medium	Also affects ansible
GHSA-2pfh-q76x-gwvm Improper Input Validation and Command Injection in Ansible	High	Also affects ansible
PYSEC-2021-126 A flaw was found in Ansible if an ansible user sets ANSIBLE_ASYNC_DIR to a subdirectory of a world writable directory.	Not rated yet	Also affects ansible
GHSA-r6h7-5pq2-j77h Insufficiently random values in Ansible	Medium	Also affects ansible

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor