Ansible vulnerable to Exposure of Resource to Wrong Sphere and Insecure Temporary File
Red Hat Ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
Red Hat Ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
2.9.6A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with "umask 77 && mkdir -p <dir>"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'.
From the CVE record · redhat
Ansible Engine has a race condition when a playbook runs a module as an unprivileged become user. A local attacker can identify the temporary directory through /proc/<pid>/cmdline and, if the directory already exists under their ownership, gain control of the become user.
Teams running Red Hat Ansible or the PyPI ansible package should check the affected 2.7, 2.8, and 2.9 releases listed in the advisory.