Skip to content
Fencer Intel
critical 9.8

CVE-2014-4657 json

Ansible Remote Code Execution

published 2020-02-20 6 y ago modified 2026-06-17 4 mo ago also GHSA-qg47-5px9-32g7 , PYSEC-2020-199 , EUVD-2020-0010

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.5%
EPSS 4.5% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrary code via crafted instructions.

Patch / fix

  • pypi ansible 1.5.4
  • redhat ansible 1.5.4
  • ansible Debian 14, Debian 13, Debian 12 1.5.5+dfsg-1

debian advisories DEBIAN-CVE-2014-4657

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-4657 updated cvss 9.8

ansible: improper restriction of code subset allows remote arbitrary code execution via crafted instructions

  • Red Hat CloudForms Management Engine 5 ansible Red Hat Ansible Engine 2 ansible, ansible-test Red Hat Ansible Tower 3 ansible Red Hat Ceph Storage 2 ansible Red Hat Ceph Storage 3 ansible Red Hat OpenStack Platform 10 (Newton) ansible
    +2 more products
    Red Hat OpenStack Platform 13 (Queens) ansible Red Hat Storage 3 ansible
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.51% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi ansible
<1.5.4
1.5.4

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.