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

Published: 2020-03-09 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-1737 is rated Low Risk (39.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.36%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-1737

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.16% 0.36% +0.21%
2 2026-04-21 0.07% 0.16% +0.08%
3 2025-06-19 — 0.07% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-1737

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 0.8 6.0 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
4.6 2.0 MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 3.9 6.4 [email protected]

Weakness enumeration for CVE-2020-1737

GitHub Security Advisory for CVE-2020-1737

OS Trackers for CVE-2020-1737

vendor priority summary link
alpine high CVE-2020-1737: 2 source package rows (ansible, ansible-base); 5 state rows across 5 repos (3.10-main, 3.11-main, 3.12-main, edge-community, edge-main); fixed 5, open 0. https://security.alpinelinux.org/vuln/CVE-2020-1737
debian unimportant CVE-2020-1737 unimportant priority: Debian including 1 source packages (ansible), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-1737
gentoo normal CVE-2020-1737: 1 GLSA(s) (202006-11), 1 atom(s) (app-admin/ansible); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-1737
redhat medium — https://access.redhat.com/security/cve/CVE-2020-1737
suse high CVE-2020-1737 severity important: SUSE including 116 source package names (ansible-10-10.6.0-1.1, ansible-11-11.11.0-1.1, …), 248 product×package rows across 10 product lines (HPE Helion OpenStack 8, HPE Helion OpenStack Cloud 8, … (10 product lines)): Fixed 246, Known Not Affected 2. https://www.suse.com/security/cve/CVE-2020-1737/
ubuntu medium CVE-2020-1737 medium priority: Ubuntu including 1 source packages (ansible), 17 status rows across 17 suites (bionic, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 11, needs-triage 5, ignored 1. https://ubuntu.com/security/CVE-2020-1737

Affected software / configurations for CVE-2020-1737

Vendor Product Version Raw CPE
redhat ansible_engine < 2.7.17 cpe:2.3:a:redhat:ansible_engine:*:*:*:*:*:*:*:*
redhat ansible_engine >= 2.8.0, < 2.8.9 cpe:2.3:a:redhat:ansible_engine:*:*:*:*:*:*:*:*
redhat ansible_engine >= 2.9.0, < 2.9.6 cpe:2.3:a:redhat:ansible_engine:*:*:*:*:*:*:*:*
redhat ansible_tower <= 3.3.4 cpe:2.3:a:redhat:ansible_tower:*:*:*:*:*:*:*:*
redhat ansible_tower >= 3.4.0, <= 3.4.5 cpe:2.3:a:redhat:ansible_tower:*:*:*:*:*:*:*:*
redhat ansible_tower >= 3.5.0, <= 3.5.5 cpe:2.3:a:redhat:ansible_tower:*:*:*:*:*:*:*:*
redhat ansible_tower >= 3.6.0, <= 3.6.3 cpe:2.3:a:redhat:ansible_tower:*:*:*:*:*:*:*:*

References for CVE-2020-1737

cvelogic Threat Intelligence