CVE-2020-1737: 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

Routine

HIGH 7.5WATCHLISTUPGRADEUPGRADE

CVE-2020-1737 is a high-severity flaw (CVSS 7.5) affecting ansible engine, ansible tower. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 70%)
CISA exploited list	No
Weakness	CWE-22
Published	2020-03-09
Last modified	2026-06-17

Publisher (CNA): Red Hat, Inc. · Vendor: redhat

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-03-09 16:15 UTCPublished CVE record published
2026-06-17 03:02 UTCUpdated Record last modified

redhat ansible engine UPGRADE

Affected: < 2.7.17 · >= 2.8.0 and < 2.8.9 · >= 2.9.0 and < 2.9.6

Fixed in: 2.7.17, 2.8.9, 2.9.6

Safe to downgrade to: a release before 2.8.0

1. Check installed version

apt-cache policy ansible-engine || rpm -q ansible-engine || ansible-engine --version

2. UPGRADE to 2.7.17 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ansible-engine

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ansible-engine

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.8.0 (Debian / Ubuntu)

apt-cache madison ansible-engine sudo apt install ansible-engine=<VERSION_BEFORE_2.8.0> sudo apt-mark hold ansible-engine

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ansible-engine sudo dnf downgrade ansible-engine-<VERSION_BEFORE_2.8.0> sudo dnf versionlock add ansible-engine

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

redhat ansible tower UPGRADE

Affected: <= 3.3.4 · >= 3.4.0 and <= 3.4.5 · >= 3.5.0 and <= 3.5.5 · >= 3.6.0 and <= 3.6.3

Fixed in: newer than 3.6.3

Safe to downgrade to: a release before 3.4.0

1. Check installed version

apt-cache policy ansible-tower || rpm -q ansible-tower || ansible-tower --version

2. UPGRADE to newer than 3.6.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ansible-tower

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ansible-tower

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.4.0 (Debian / Ubuntu)

apt-cache madison ansible-tower sudo apt install ansible-tower=<VERSION_BEFORE_3.4.0> sudo apt-mark hold ansible-tower

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list ansible-tower sudo dnf downgrade ansible-tower-<VERSION_BEFORE_3.4.0> sudo dnf versionlock add ansible-tower

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-1737?

ansible engine: upgrade to 2.7.17, 2.8.9, 2.9.6; ansible tower: upgrade to newer than 3.6.3. Exact commands for each OS are on this page.

Is CVE-2020-1737 being exploited?

CVE-2020-1737 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-1737 affect?

CVE-2020-1737 affects ansible engine, ansible tower. Severity is high (CVSS 7.5). 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

How urgent is CVE-2020-1737?

Priority 39/100. High severity; On your watchlist

Software pages

Ansible vulnerabilities

Related CVEs

CVE-2021-3620 MEDIUM 5.5 DOWNGRADE UPGRADE A flaw was found in Ansible Engine's ansible-connection module, where sensitive information such as the Ansibl
CVE-2021-3583 HIGH 7.1 DOWNGRADE UPGRADE A flaw was found in Ansible, where a user's controller is vulnerable to template injection
CVE-2021-20228 HIGH 7.5 DOWNGRADE DOWNGRADE A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protec
CVE-2020-1753 MEDIUM 5.0 UPGRADE UPGRADE A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x ver
CVE-2020-1746 MEDIUM 5.0 UPGRADE UPGRADE A flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before

References

← Back to latest CVEs