CVE-2020-1736

ansible: atomic_move primitive sets permissive permissions

Published Mar 16, 2020 CVSS 3.1 · 2.2 Low EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2020-0030 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.
Github GHSA Github GHSA GHSA-x7jh-595q-wq82 Incorrect Permission Assignment for Critical Resource in Ansible
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 4, 2024, 6:46 AM
Reserved
Nov 27, 2019, 12:00 AM
Status
Modified
Published
Mar 16, 2020, 4:15 PM
Modified
Jun 17, 2026, 3:02 AM
Severity
Low
Public date
Feb 18, 2020, 12:00 AM