CVE-2020-1736: Incorrect Permission Assignment for Critical Resource in Ansible
(updated )
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.
References
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2020-1736
- github.com/advisories/GHSA-x7jh-595q-wq82
- github.com/ansible/ansible
- github.com/ansible/ansible/issues/67794
- github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-8.yaml
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2NYYQP2XJB2TTRP6AKWVMBSPB2DFJNKD
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BPNZWBAUP4ZHUR6PO7U6ZXEKNCX62KZ7
- nvd.nist.gov/vuln/detail/CVE-2020-1736
- security.gentoo.org/glsa/202006-11
Code Behaviors & Features
Detect and mitigate CVE-2020-1736 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →