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
Noroxi assessment
Priority: Monitor (action score 27/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: 1.8% (FIRST EPSS); higher than 78.8% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: ansible (Alpine:v3.10) 2.8.8-r0; ansible (Alpine:v3.9) 2.7.16-r0; ansible (Debian:10) 2.7.7+dfsg-1+deb10u1.
Low priority for now. Upgrade to ansible (Alpine:v3.10) 2.8.8-r0; ansible (Alpine:v3.9) 2.7.16-r0; ansible (Debian:10) 2.7.7+dfsg-1+deb10u1 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
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.
- Published
- Jan 2, 2020
- Updated
- Jun 16, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-117
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
CNA vs NVD score
- NVD
- 6.5
- CNA · redhat
- 5.7
- 0.8 point gap
CVSS:3.0/AV:N/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 | ansible tower | cpe:2.3:a:redhat:ansible_tower |
| redhat | ceph storage | cpe:2.3:a:redhat:ceph_storage |
| redhat | cloudforms management engine | cpe:2.3:a:redhat:cloudforms_management_engine |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| opensuse | backports sle | cpe:2.3:a:opensuse:backports_sle |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- opensuse backports sle15.0
- opensuse leap15.1
- redhat ansible2.7.0 and later · before 2.7.15
- redhat ansible2.8.0 and later · before 2.8.7
- redhat ansible2.9.0 and later · before 2.9.1
- redhat ansible tower3.0
- redhat ceph storage3.0
- redhat cloudforms management engine5.0
- redhat enterprise linux6.0
- redhat enterprise linux7.0
- redhat enterprise linux8.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 Ansible
- Ansible versions 2.9.x before 2.9.1, Ansible versions 2.8.x before 2.8.7, Ansible versions 2.7.x before 2.7.15affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | ansible | from 2.7.0 · before 2.8.8-r0 | 2.8.8-r0 |
| Alpine:v3.9 | ansible | from 2.7.0 · before 2.7.16-r0 | 2.7.16-r0 |
| Debian:10 | ansible | before 2.7.7+dfsg-1+deb10u1 | 2.7.7+dfsg-1+deb10u1 |
| Debian:12 | ansible | before 2.9.2+dfsg-1 | 2.9.2+dfsg-1 |
| openSUSE:Leap 15.1 | ansible | before 2.9.6-lp151.2.7.1 | 2.9.6-lp151.2.7.1 |
| openSUSE:Tumbleweed | ansible-10 | before 10.6.0-1.1 | 10.6.0-1.1 |
| openSUSE:Tumbleweed | ansible-11 | before 11.11.0-1.1 | 11.11.0-1.1 |
| openSUSE:Tumbleweed | ansible-12 | before 12.2.0-1.1 | 12.2.0-1.1 |
| openSUSE:Tumbleweed | ansible-13 | before 13.7.0-1.1 | 13.7.0-1.1 |
| openSUSE:Tumbleweed | ansible-9 | before 9.8.0-1.1 | 9.8.0-1.1 |
| PyPI | ansible | from 2.7.0 · before 2.7.15 | 2.7.15 |
| PyPI | ansible | from 2.7.0a1 · before 2.7.15 | 2.7.15 |
| PyPI | ansible | from 2.8.0 · before 2.8.7 | 2.8.7 |
| PyPI | ansible | from 2.8.0a1 · before 2.8.7 | 2.8.7 |
| PyPI | ansible | from 2.9.0 · before 2.9.1 | 2.9.1 |
| PyPI | ansible | from 2.9.0a1 · before 2.9.1 | 2.9.1 |
| Red Hat:ansible_engine:2.7::el7 | ansible | before 0:2.7.15-1.el7ae | 0:2.7.15-1.el7ae |
| Red Hat:ansible_engine:2.8::el7 | ansible | before 0:2.8.7-1.el7ae | 0:2.8.7-1.el7ae |
| Red Hat:ansible_engine:2.8::el8 | ansible | before 0:2.8.7-1.el8ae | 0:2.8.7-1.el8ae |
| Red Hat:ansible_engine:2.9::el7 | ansible | before 0:2.9.1-1.el7 | 0:2.9.1-1.el7 |
| Red Hat:ansible_engine:2.9::el7 | ansible-test | before 0:2.9.1-1.el7 | 0:2.9.1-1.el7 |
| Red Hat:ansible_engine:2.9::el8 | ansible | before 0:2.9.1-1.el8 | 0:2.9.1-1.el8 |
| Red Hat:ansible_engine:2.9::el8 | ansible-test | before 0:2.9.1-1.el8 | 0:2.9.1-1.el8 |
| SUSE:Package Hub 15 SP1 | ansible | before 2.9.6-bp151.3.6.1 | 2.9.6-bp151.3.6.1 |
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
- CVE-2014-4966Ansible before 1.6.7 does not prevent inventory data with "{{" and "lookup" substrings, and does not prevent remote data with "{{" substring40Plan
- CVE-2017-7550A flaw was found in the way Ansible (2.3.x before 2.3.3, and 2.4.x before 2.4.1) passed certain parameters to the jenkins_plugin module.40Plan
- CVE-2016-8628Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller.37Monitor
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 |
|---|---|---|
| alpine:ansible | 2.8.8-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:ansible | 2.9.2+dfsg-1 · Debian:12 | Package registry (OSV) |
| opensuse:ansible | 2.9.6-lp151.2.7.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| opensuse:ansible-10 | 10.6.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-11 | 11.11.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-12 | 12.2.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-13 | 13.7.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-9 | 9.8.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:ansible | 2.7.15 | Package registry (OSV) |
| PyPI:ansible | 2.8.7 | Package registry (OSV) |
| PyPI:ansible | 2.9.1 | Package registry (OSV) |
| red hat:ansible | 0:2.7.15-1.el7ae · Red Hat:ansible_engine:2.7::el7 | Package registry (OSV) |
| red hat:ansible-test | 0:2.9.1-1.el7 · Red Hat:ansible_engine:2.9::el7 | Package registry (OSV) |
| suse:ansible | 2.9.6-bp151.3.6.1 · SUSE:Package Hub 15 SP1 | Package registry (OSV) |
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
- Anyone who can reach it over the internet 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
- Network
- 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:N/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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.