QID 356226

a flaw was found in ansible engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean.
An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection. (
( CVE-2020-10684) 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. (
( CVE-2020-10685) an archive traversal flaw was found in all ansible-engine versions 2.9.x prior to 2.9.7, when running ansible-galaxy collection install.
When extracting a collection .tar.gz file, the directory is created without sanitizing the filename.
An attacker could take advantage to overwrite any file within the system. (
When ansible needs to run a module with become user, the temporary directory is created in /var/tmp.
( CVE-2020-1753)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.