CVE-2020-1737: Path Traversal
A flaw was found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the winunzip module as the extracted file(s) are not checked if they belong to the destination folder. An attacker could take advantage of this flaw by crafting an archive anywhere in the file system, using a path traversal. This issue is fixed in 2.10.
Other sources
Extract-Zip function in winunzip module does not check if the extracted path belongs to the destination folder. This could lead to path traversal on a crafted archive.
— Red Hat
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/ansible-engineto a version that resolves this vulnerability.Fixed in 2.7.17 - Upgrade
Upgrade
redhat/ansible-engineto a version that resolves this vulnerability.Fixed in 2.8.11 - Upgrade
Upgrade
redhat/ansible-engineto a version that resolves this vulnerability.Fixed in 2.9.7 - Upgrade
Upgrade
pip/ansibleto a version that resolves this vulnerability.Fixed in 2.7.17 - Upgrade
Upgrade
pip/ansibleto a version that resolves this vulnerability.Fixed in 2.9.6 - Upgrade
Upgrade
pip/ansibleto a version that resolves this vulnerability.Fixed in 2.8.9 - Upgrade
Upgrade
ansibleto a version that resolves this vulnerability.Fixed in 2.10
Event History
Frequently Asked Questions
What is CVE-2020-1737?
CVE-2020-1737 is a vulnerability found in Ansible 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior when using the Extract-Zip function from the win_unzip module as the extracted file(s) are not checked if they belong to the destination folder.
How severe is CVE-2020-1737?
CVE-2020-1737 has a severity rating of 7.8 (high).
How can an attacker exploit CVE-2020-1737?
An attacker could take advantage of CVE-2020-1737 by crafting a malicious archive file.
Which versions of Ansible are affected by CVE-2020-1737?
Ansible versions 2.7.17 and prior, 2.8.9 and prior, and 2.9.6 and prior are affected by CVE-2020-1737.
Are there any remedies or fixes available for CVE-2020-1737?
Yes, for Red Hat users, updating to Ansible version 2.7.18, 2.8.11, or 2.9.7 will fix the vulnerability. For pip installation, updating to Ansible version 2.7.18, 2.8.10, or 2.9.7 will resolve the issue.