LiveActive security incident?Get immediate response
CVE Record

CVE-2014-4678: The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows rem...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2014-4678 is a legacy Ansible flaw where the safe_eval function did not sufficiently restrict evaluated instructions. In affected versions before 1.6.4, crafted input could allow arbitrary code execution. Business urgency is highest only where very old Ansible versions remain in use, especially around automation that can reach production systems.

Executive priority

Prioritize as a legacy exposure cleanup with high impact if present. Most organizations should first confirm whether Ansible before 1.6.4 exists anywhere, then remove or upgrade it promptly.

Technical view

Ansible before 1.6.4 incompletely constrained safe_eval, leaving a bypass after the CVE-2014-4657 fix. The CVE record states remote attackers could execute arbitrary code through crafted instructions. The bundle does not provide CVSS, CWE, detailed exploit prerequisites, or confirmed in-the-wild exploitation.

Likely exposure

Exposure is limited to environments still running Ansible before 1.6.4. Because Ansible commonly has privileged access to managed hosts, any remaining affected installation should be treated as operationally significant until upgraded or removed.

Exploitation context

The source bundle says remote attackers may execute arbitrary code via crafted instructions. CISA KEV is false, and no provided source confirms active exploitation. Public details in the bundle are sparse, so exploitation conditions should be verified against vendor and distribution advisories.

Researcher notes

The record ties this issue to an incomplete fix for CVE-2014-4657. Useful follow-up is comparing the referenced Ansible commit and 2014 advisories to understand safe_eval hardening and affected package backports.

Mitigation direction

  • Upgrade affected Ansible installations to 1.6.4 or later supported releases.
  • Remove unsupported legacy Ansible packages where automation is no longer required.
  • Check distribution advisories for Debian, Gentoo, and FreeBSD package status.
  • Restrict who can submit or influence Ansible instructions and automation inputs.
  • Review vendor guidance before applying any environment-specific workaround.

Validation and detection

  • Inventory all hosts and build images for Ansible versions before 1.6.4.
  • Check package manager records against vendor and distribution fixed versions.
  • Identify automation paths accepting untrusted playbooks, variables, inventory, or job inputs.
  • Confirm legacy Ansible controllers are not exposed to untrusted users or networks.
  • Document remediation evidence for each affected system.
Prepared
Confidence
medium
Sources
9

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-4678 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
8Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAnsiblebefore 1.6.4Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.