Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible
Red Hat Ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
Red Hat Ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
2.9.7A 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.
From the CVE record · redhat
Ansible Engine and Tower can leave decrypted vault data in a temporary directory when modules such as copy, script, or unarchive decrypt vault files. If /tmp is on the root partition rather than tmpfs, the data can remain on disk after shutdown, creating an exposure for someone with access to the stopped host.
Check Ansible Engine 2.7.x before 2.7.17, 2.8.x before 2.8.11, or 2.9.x before 2.9.7, and Ansible Tower versions up to and including 3.4.5, 3.5.5, or 3.6.3.