Insecure Temporary File Affecting ansible package, versions <0:2.9.7-1.el7ae


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.09% (41st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Insecure Temporary File vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-ANSIBLE-3375468
  • published26 Mar 2023
  • disclosed18 Feb 2020

Introduced: 18 Feb 2020

CVE-2020-1733  (opens in a new tab)
CWE-377  (opens in a new tab)

How to fix?

Upgrade RHEL:7 ansible to version 0:2.9.7-1.el7ae or higher.
This issue was patched in RHSA-2020:1541.

NVD Description

Note: Versions mentioned in the description apply only to the upstream ansible package and not the ansible package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

A 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'.

CVSS Scores

version 3.1