CVE-2017-7481: Ansible fails to properly mark lookup-plugin results as unsafe

CVE-2017-7481 · Severity: low · CVSS 3.1 · Published 2018-07-19

Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

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

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=2.3.0.0,fixed=2.3.1.0, GIT:introduced=0,fixed=ed56f51f185a1ffd7ea57130d260098686fcc7c2|ECOSYSTEM:introduced=0,fixed=2.3.1.0,introduced=2.3.2.0,fixed=2.4.0.0

Identifiers

  • CVE-2017-7481
  • GHSA-w578-j992-554x
  • PYSEC-2018-41

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