Incorrect Permission Assignment for Critical Resource in Ansible
Red Hat ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
Red Hat ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
From the CVE record · redhat
Ansible Engine's atomic_move primitive cannot specify a file mode when moving a file. If the destination does not exist, the resulting file can be world-readable; if it exists, its permissions can become less restrictive before the move, potentially exposing sensitive data. The input does not specify attacker access requirements or user interaction.
Engineers running the PyPI ansible package in affected 2.7.x, 2.8.x, or 2.9.x releases, or version 2.10.0, should check their installations.