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 mo
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Red Hat Ansible 2.10.
Low priority for now. Upgrade to Red Hat Ansible 2.10 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- Mar 9, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-22
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 7.8
- CNA · redhat
- 7.5
- 0.3 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | ansible engine | cpe:2.3:a:redhat:ansible_engine |
| redhat | ansible tower | cpe:2.3:a:redhat:ansible_tower |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat ansible enginebefore 2.7.17
- redhat ansible engine2.8.0 and later · before 2.8.9
- redhat ansible engine2.9.0 and later · before 2.9.6
- redhat ansible towerup to 3.3.4 inclusive
- redhat ansible tower3.4.0 and later · up to 3.4.5 inclusive
- redhat ansible tower3.5.0 and later · up to 3.5.5 inclusive
- redhat ansible tower3.6.0 and later · up to 3.6.3 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat Ansible
- 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior, fixed in 2.10affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | ansible | before 2.8.9-r0 | 2.8.9-r0 |
| Alpine:v3.11 | ansible | before 2.9.6-r0 | 2.9.6-r0 |
| Alpine:v3.13 | ansible-base | before 2.9.6-r0 | 2.9.6-r0 |
| Alpine:v3.9 | ansible | before 2.7.17-r0 | 2.7.17-r0 |
| Debian:12 | ansible | before 2.9.7+dfsg-1 | 2.9.7+dfsg-1 |
| openSUSE:Leap 15.3 | ansible | before 2.9.21-bp153.2.3.1 | 2.9.21-bp153.2.3.1 |
| PyPI | ansible | from 2.8.0 · before 2.8.9 | 2.8.9 |
| PyPI | ansible | from 2.8.0a1 · before 2.8.9 | 2.8.9 |
| PyPI | ansible | from 2.9.0 · before 2.9.6 | 2.9.6 |
| PyPI | ansible | from 2.9.0a1 · before 2.9.6 | 2.9.6 |
| PyPI | ansible | before 2.7.17 | 2.7.17 |
| Red Hat:ansible_engine:2.7::el7 | ansible | before 0:2.7.17-1.el7ae | 0:2.7.17-1.el7ae |
| Red Hat:ansible_engine:2.8::el7 | ansible | before 0:2.8.11-1.el7ae | 0:2.8.11-1.el7ae |
| Red Hat:ansible_engine:2.8::el8 | ansible | before 0:2.8.11-1.el8ae | 0:2.8.11-1.el8ae |
| Red Hat:ansible_engine:2.9::el7 | ansible | before 0:2.9.7-1.el7ae | 0:2.9.7-1.el7ae |
| Red Hat:ansible_engine:2.9::el7 | ansible-test | before 0:2.9.7-1.el7ae | 0:2.9.7-1.el7ae |
| Red Hat:ansible_engine:2.9::el8 | ansible | before 0:2.9.7-1.el8ae | 0:2.9.7-1.el8ae |
| Red Hat:ansible_engine:2.9::el8 | ansible-test | before 0:2.9.7-1.el8ae | 0:2.9.7-1.el8ae |
| SUSE:Package Hub 15 SP3 | ansible | before 2.9.21-bp153.2.3.1 | 2.9.21-bp153.2.3.1 |
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-20228A flaw was found in the Ansible Engine 2.9.18, where sensitive info is not masked by default and is not protected by the no_log feature when31Monitor
- CVE-2019-14846In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG 31Monitor
- CVE-2018-16837Ansible "User" module leaks any data which is passed on as a parameter to ssh-keygen.31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-14858Oct 14, 2019 · A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5.22Monitor
- ← EarlierCVE-2020-1734Mar 3, 2020 · A flaw was found in the pipe lookup plugin of ansible.29Monitor
- Later →CVE-2020-1753Mar 16, 2020 · A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all 22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Red Hat Ansible | 2.10 · description | Vendor (CNA) |
| alpine:ansible | 2.8.9-r0 · Alpine:v3.10 | Package registry (OSV) |
| alpine:ansible-base | 2.9.6-r0 · Alpine:v3.13 | Package registry (OSV) |
| debian:ansible | 2.9.7+dfsg-1 · Debian:12 | Package registry (OSV) |
| opensuse:ansible | 2.9.21-bp153.2.3.1 · openSUSE:Leap 15.3 | Package registry (OSV) |
| PyPI:ansible | 2.7.17 | Package registry (OSV) |
| PyPI:ansible | 2.8.9 | Package registry (OSV) |
| PyPI:ansible | 2.9.6 | Package registry (OSV) |
| red hat:ansible | 0:2.9.7-1.el7ae · Red Hat:ansible_engine:2.9::el7 | Package registry (OSV) |
| red hat:ansible-test | 0:2.9.7-1.el7ae · Red Hat:ansible_engine:2.9::el7 | Package registry (OSV) |
| suse:ansible | 2.9.21-bp153.2.3.1 · SUSE:Package Hub 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/ansible/ansible/issues/67795
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FWDK3QUVBULS3Q3PQTGEKUQYPSNOU5M3/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QT27K5ZRGDPCH7GT3DRI3LO4IVDVQUB7/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/U3IMV3XEIUXL6S4KPLYYM4TVJQ2VNEP2/
- security.gentoo.org/glsa/202006-11
Vendor advisories and official records. Exploit/PoC links are deliberately left out.