CVE-2014-4678: Ansible Code Injection Vulnerability

CVE-2014-4678 · Severity: low · CVSS 3.1 · Published 2020-02-20

The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions. NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-4657.

Technologies: ansible (PyPI). Vendors: PyPI.

Quick answers

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

Affected products

  • ansible (PyPI) ECOSYSTEM:introduced=0,fixed=1.6.4, GIT:introduced=0,fixed=5429b85b9f6c2e640074176f36ff05fd5e4d1916|ECOSYSTEM:introduced=0,fixed=1.6.4

Identifiers

  • CVE-2014-4678
  • GHSA-66c7-5pwv-mm3j
  • PYSEC-2020-203

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