7.8
CWE
22
Advisory Published
CVE Published
Advisory Published
Updated

CVE-2020-1737: Path Traversal

First published: Wed Feb 12 2020(Updated: )

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 win_unzip 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.

Credit: secalert@redhat.com secalert@redhat.com

Affected SoftwareAffected VersionHow to fix
Redhat Ansible Engine<2.7.17
Redhat Ansible Engine>=2.8.0<2.8.9
Redhat Ansible Engine>=2.9.0<2.9.6
Redhat Ansible Tower<=3.3.4
Redhat Ansible Tower>=3.4.0<=3.4.5
Redhat Ansible Tower>=3.5.0<=3.5.5
Redhat Ansible Tower>=3.6.0<=3.6.3
redhat/ansible-engine<2.7.17
2.7.17
redhat/ansible-engine<2.8.11
2.8.11
redhat/ansible-engine<2.9.7
2.9.7
pip/ansible>=0<2.7.17
2.7.17
pip/ansible>=2.9.0a1<2.9.6
2.9.6
pip/ansible>=2.8.0a1<2.8.9
2.8.9

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Reference Links

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203