Ansible-core: possible information leak in tasks that ignore ansible_no_log configuration
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: www.ansible.com/ ansible 2.14.4, 2.15.9, 2.16.3.
Low priority for now. Upgrade to www.ansible.com/ ansible 2.14.4, 2.15.9, 2.16.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An information disclosure flaw was found in ansible-core due to a failure to respect the ANSIBLE_NO_LOG configuration in some scenarios. Information is still included in the output in certain tasks, such as loop items. Depending on the task, this issue may include sensitive information, such as decrypted secret values.
- BDU:2024-01561
- GHSA-h24r-m9qc-pvpg
- ALSA-2024:2246
- ALSA-2024:3043
- openSUSE-SU-2024:14251-1
- openSUSE-SU-2024:14537-1
- openSUSE-SU-2025:15638-1
- openSUSE-SU-2025:15754-1
- openSUSE-SU-2026:10945-1
- PYSEC-2024-36
- RHSA-2024:0733
- RHSA-2024:2246
- RHSA-2024:3043
- RLSA-2024:3043
- SUSE-SU-2024:1427-1
- SUSE-SU-2024:1509-1
- Published
- Feb 6, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 22th percentile
- CWE
- CWE-117
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.5
- CNA · redhat
- 5.0
- 0.5 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | ansible | cpe:2.3:a:redhat:ansible |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| redhat | ansible automation platform | cpe:2.3:a:redhat:ansible_automation_platform |
| redhat | ansible developer | cpe:2.3:a:redhat:ansible_developer |
| redhat | ansible inside | cpe:2.3:a:redhat:ansible_inside |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora38
- fedoraproject fedora39
- redhat ansible2.16.0 and later · before 2.16.3
- redhat ansiblebefore 2.14.4
- redhat ansible2.15.0 and later · before 2.15.9
- redhat ansible automation platform2.4
- redhat ansible developer1.1
- redhat ansible inside1.2
- redhat enterprise linux8.0
- redhat enterprise linux9.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Red Hat Ansible Automation Platform 2.4 for RHEL 8
- 1:2.15.9-1.el8ap and laternot affected · rpm
Red Hat Red Hat Ansible Automation Platform 2.4 for RHEL 9
- 1:2.15.9-1.el9ap and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 8
- 0:2.16.3-2.el8 and laternot affected · rpm
Red Hat Red Hat Enterprise Linux 9
- 1:2.14.14-1.el9 and laternot affected · rpm
www.ansible.com/ ansible
- 2.14.0 and later · before 2.14.4affected · semver
- 2.15.0 and later · before 2.15.9affected · semver
- 2.16.0 and later · before 2.16.3affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | ansible-core | before 2.16.3-2.el8 | 2.16.3-2.el8 |
| AlmaLinux:8 | ansible-test | before 2.16.3-2.el8 | 2.16.3-2.el8 |
| AlmaLinux:9 | ansible-core | before 1:2.14.14-1.el9 | 1:2.14.14-1.el9 |
| AlmaLinux:9 | ansible-test | before 1:2.14.14-1.el9 | 1:2.14.14-1.el9 |
| Debian:12 | ansible | before 5.4.0-1 | 5.4.0-1 |
| Debian:12 | ansible-core | before 2.14.16-0+deb12u1 | 2.14.16-0+deb12u1 |
| Debian:13 | ansible-core | before 2.16.5-1 | 2.16.5-1 |
| openSUSE:Leap 15.5 | ansible | before 2.9.27-150000.1.17.2 | 2.9.27-150000.1.17.2 |
| openSUSE:Leap 15.5 | dracut-saltboot | before 0.1.1710765237.46af599-150000.1.53.2 | 0.1.1710765237.46af599-150000.1.53.2 |
| openSUSE:Leap 15.5 | golang-github-prometheus-promu | before 0.14.0-150000.3.18.2 | 0.14.0-150000.3.18.2 |
| openSUSE:Leap 15.5 | POS_Image-Graphical7 | before 0.1.1710765237.46af599-150000.1.21.2 | 0.1.1710765237.46af599-150000.1.21.2 |
| openSUSE:Leap 15.5 | POS_Image-JeOS7 | before 0.1.1710765237.46af599-150000.1.21.2 | 0.1.1710765237.46af599-150000.1.21.2 |
| openSUSE:Leap 15.5 | spacecmd | before 4.3.27-150000.3.116.2 | 4.3.27-150000.3.116.2 |
| openSUSE:Tumbleweed | ansible-core | before 2.16.9-1.1 | 2.16.9-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.17 | before 2.17.6-1.1 | 2.17.6-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.18 | before 2.18.10-2.1 | 2.18.10-2.1 |
| openSUSE:Tumbleweed | ansible-core-2.19 | before 2.19.4-1.1 | 2.19.4-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.20 | before 2.20.6-1.1 | 2.20.6-1.1 |
| PyPI | ansible-core | from 2.15.0 · before 2.15.9 | 2.15.9 |
| PyPI | ansible-core | from 2.16.0 · before 2.16.3 | 2.16.3 |
| PyPI | ansible-core | before 2.14.14 | 2.14.14 |
| PyPI | ansible-core | before 2.14.4 | 2.14.4 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | ansible-core | before 1:2.15.9-1.el8ap | 1:2.15.9-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | ansible-core | before 1:2.15.9-1.el9ap | 1:2.15.9-1.el9ap |
+29
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-4678The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrar41Plan
- CVE-2014-4657The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrar40Plan
- CVE-2014-4967Multiple argument injection vulnerabilities in Ansible before 1.6.7 allow remote attackers to execute arbitrary code by leveraging access to40Plan
Published before and after this one in the same product
- ← EarlierCVE-2021-20180Mar 16, 2022 · A flaw was found in ansible module where credentials are disclosed in the console log by default and not protected by the security feature w22Monitor
- ← EarlierCVE-2022-3697Oct 28, 2022 · A flaw was found in Ansible in the amazon.aws collection when using the tower_callback parameter from the amazon.aws.ec2_instance module.30Monitor
- ← EarlierCVE-2023-5764Dec 12, 2023 · Ansible: template injection31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| www.ansible.com/ ansible | 2.14.4 | Vendor (CNA) |
| www.ansible.com/ ansible | 2.15.9 | Vendor (CNA) |
| www.ansible.com/ ansible | 2.16.3 | Vendor (CNA) |
| almalinux:ansible-core | 1:2.14.14-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:ansible-test | 1:2.14.14-1.el9 · AlmaLinux:9 | Package registry (OSV) |
| debian:ansible | 5.4.0-1 · Debian:12 | Package registry (OSV) |
| debian:ansible-core | 2.14.16-0+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:ansible | 2.9.27-150000.1.17.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:ansible-core | 2.16.9-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.17 | 2.17.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.18 | 2.18.10-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.19 | 2.19.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.20 | 2.20.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:dracut-saltboot | 0.1.1710765237.46af599-150000.1.53.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:golang-github-prometheus-promu | 0.14.0-150000.3.18.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:POS_Image-Graphical7 | 0.1.1710765237.46af599-150000.1.21.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:POS_Image-JeOS7 | 0.1.1710765237.46af599-150000.1.21.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| opensuse:spacecmd | 4.3.27-150000.3.116.2 · openSUSE:Leap 15.5 | Package registry (OSV) |
| PyPI:ansible-core | 2.14.14 | Package registry (OSV) |
| PyPI:ansible-core | 2.14.4 | Package registry (OSV) |
| PyPI:ansible-core | 2.15.9 | Package registry (OSV) |
| PyPI:ansible-core | 2.16.3 | Package registry (OSV) |
| red hat:ansible-core | 1:2.15.9-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:ansible-test | 1:2.14.14-1.el9 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.1-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| rocky linux:ansible-core | 0:2.16.3-2.el8 · Rocky Linux:8 | Package registry (OSV) |
| suse:ansible | 2.9.27-150000.1.17.2 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:ansible | 2.9.27-159000.3.12.2 · SUSE:Manager Client Tools 15-BETA | Package registry (OSV) |
| suse:dracut-saltboot | 0.1.1710765237.46af599-150000.1.53.2 · SUSE:Manager Client Tools 15 | Package registry (OSV) |
| suse:dracut-saltboot | 0.1.1710765237.46af599-159000.3.33.2 · SUSE:Manager Client Tools 15-BETA | Package registry (OSV) |
+18
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-117 · Improper Output Neutralization for LogsCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- access.redhat.com/errata/RHSA-2024:2246
- access.redhat.com/errata/RHSA-2024:3043
- access.redhat.com/security/cve/CVE-2024-0690
- bugzilla.redhat.com/show_bug.cgi?id=2259013
- github.com/ansible/ansible/pull/82565
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IZQGCRDSZL7ONCULMB6ZUHOE4L44KIBP/
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VDYSWOCPZMNRU5LWKIEBW4WGWLMTU7WQ/
- security.netapp.com/advisory/ntap-20250117-0001/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.