Is CVE-2020-10691 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2020-10691 being exploited in the wild.

How severe is CVE-2020-10691?

Low severity, with a CVSS score of 3.1, published 30 April 2020.

Which products and versions are affected?

ansible (PyPI) ECOSYSTEM:introduced=2.9.0,fixed=2.9.7, ECOSYSTEM:introduced=2.9.0a1,fixed=2.9.7.

Is there a fix for CVE-2020-10691?

Yes. ansible (PyPI): upgrade to 2.9.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2020-10691 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2020-10691?

Check whether you run ansible (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2020-10691: Ansible path traversal in ansible-galaxy collection install

CVE-2020-10691 · Severity: low · CVSS 3.1 · Published 2020-04-30

Ansible is an open-source automation tool used by system administrators to configure and manage infrastructure. When installing collections via ansible-galaxy, a flaw in the .tar.gz extraction process could allow a malicious collection archive to write files outside the intended directory, potentially overwriting critical system or application files. An attacker who can create or distribute a specially crafted collection could gain the ability to modify or corrupt files on systems running ansible-galaxy.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-10691 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2020-10691 being exploited in the wild.
How severe is CVE-2020-10691?: Low severity, with a CVSS score of 3.1, published 30 April 2020.
Which products and versions are affected?: ansible (PyPI) ECOSYSTEM:introduced=2.9.0,fixed=2.9.7, ECOSYSTEM:introduced=2.9.0a1,fixed=2.9.7.
Is there a fix for CVE-2020-10691?: Yes. ansible (PyPI): upgrade to 2.9.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2020-10691 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2020-10691?: Check whether you run ansible (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

ansible (PyPI): upgrade to 2.9.7 or later
```
pip install "ansible>=2.9.7"
```

Technical details

A path traversal vulnerability exists in ansible-galaxy collection install due to insufficient sanitization of filenames when extracting .tar.gz archives (CWE-22). The vulnerable component is the tarfile extraction logic in Ansible 2.9.0 through 2.9.6. When a specially crafted collection archive with path traversal sequences (e.g., "../../../") in filenames is extracted, the files are written to unintended locations outside the collection directory. An attacker must provide or control the collection archive being installed, but no authentication or network access controls beyond initial download are required. The vulnerability was patched in Ansible 2.9.7 by adding filename validation before extraction to reject paths containing traversal sequences.

Affected products

Ansible Ansible 2.9.0 through 2.9.6

Identifiers

CVE-2020-10691
GHSA-3c67-gc48-983w
PYSEC-2020-2

Timeline

2020-04-30: disclosed: CVE-2020-10691 published to NVD
2020-03-31: patched: Fix merged in PR #68596
2021-04-20: advisory: GHSA-3c67-gc48-983w published

References

https://github.com/ansible/ansible/pull/68596

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.