Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2020-1736

Incorrect Permission Assignment for Critical Resource

Published: Mar 16, 2020 | Modified: Nov 07, 2023
CVSS 3.x
3.3
LOW
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
CVSS 2.x
2.1 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
2.2 LOW
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N
Ubuntu
MEDIUM
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2020-1736
CWEhttps://cwe.mitre.org/data/definitions/732.html

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.

Weakness

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

Affected Software

Name Vendor Start Version End Version
Ansible Redhat * 2.7.16 (including)
Ansible Redhat 2.8.0 (including) 2.8.15 (excluding)
Ansible Redhat 2.9.0 (including) 2.9.13 (excluding)
Ansible_tower Redhat * 3.3.4 (including)
Ansible_tower Redhat 3.3.5 (including) 3.4.5 (including)
Ansible_tower Redhat 3.5.0 (including) 3.5.5 (including)
Ansible_tower Redhat 3.6.0 (including) 3.6.3 (including)
Ansible_tower Redhat 3.7.0 (including) 3.7.2 (including)
Cloudforms_management_engine Redhat 5.0 (including) 5.0 (including)
Openstack Redhat 13 (including) 13 (including)
Red Hat Ansible Engine 2.8 for RHEL 7 RedHat ansible-0:2.8.15-1.el7ae *
Red Hat Ansible Engine 2.8 for RHEL 8 RedHat ansible-0:2.8.15-1.el8ae *
Red Hat Ansible Tower 3.4 for RHEL 7 RedHat ansible-tower-34/ansible-tower-memcached:1.4.15-28 *
Red Hat Ansible Tower 3.4 for RHEL 7 RedHat ansible-tower-35/ansible-tower-memcached:1.4.15-28 *
Red Hat Ansible Tower 3.4 for RHEL 7 RedHat ansible-tower-37/ansible-tower-memcached-rhel7:1.4.15-28 *
Red Hat Ansible Tower 3.5 for RHEL 7 RedHat ansible-tower-35/ansible-tower:3.5.6-1 *
Ansible Ubuntu bionic *
Ansible Ubuntu eoan *
Ansible Ubuntu groovy *
Ansible Ubuntu hirsute *
Ansible Ubuntu impish *
Ansible Ubuntu kinetic *
Ansible Ubuntu lunar *
Ansible Ubuntu mantic *
Ansible Ubuntu trusty *
Ansible Ubuntu xenial *

Potential Mitigations

  • Run the code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use