A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as w
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.7.17, 2.8.11, 2.9.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.
Timeline
- CVE published
- Record last updated
Affected versions
- Red Hat Ansible
ansible-engine versions 2.7.x before 2.7.17, ansible-engine 2.8.x before 2.8.11, ansible-engine 2.9.x before 2.9.7, Ansible Tower <= 3.4.5, Ansible Tower <= 3.5.5, Ansible Tower <= 3.6.3
- ansiblePyPI
From 2.7.0a1 · fixed in 2.7.17
- ansiblePyPI
From 2.8.0a1 · fixed in 2.8.11
- ansiblePyPI
From 2.9.0a1 · fixed in 2.9.7
- ansiblePyPI
From 2.7.0 · fixed in 2.7.17; From 2.8.0 · fixed in 2.8.11; From 2.9.0 · fixed in 2.9.7