CVE-2020-25635: Ansible does not collect garbage after playbook run

CVE-2020-25635 · Severity: low · CVSS 3.1 · Published 2020-10-05

A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed. Files would remain in the bucket exposing the data. This issue affects directly data confidentiality.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2020-25635 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2020-25635 being exploited in the wild.
How severe is CVE-2020-25635?
Low severity, with a CVSS score of 3.1, published 5 October 2020.
Which products and versions are affected?
ansible (PyPI) ECOSYSTEM:introduced=0,fixed=2.10.1.
Is there a fix for CVE-2020-25635?
Yes. ansible (PyPI): upgrade to 2.10.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2020-25635?
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.10.1 or later
    pip install "ansible>=2.10.1"

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=0,fixed=2.10.1

Identifiers

  • CVE-2020-25635
  • GHSA-f556-49jc-4rvc
  • PYSEC-2020-220

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