Remote code execution via callable denylist bypass
Published Feb 20, 2020 · Updated Aug 6, 2024
Code injection in Ansible before 1.6.4 allows remote attackers to execute arbitrary code through crafted instructions. The safe_eval AST visitor rejects callable names only when they appear in a denylist, allowing any unlisted callable in attacker-controlled data to reach Python evaluation. Exploitation requires control over instructions evaluated by the control node, and resulting code runs with the Ansible process's privileges.
Summary
What happened
Code injection in Ansible before 1.6.4 allows remote attackers to execute arbitrary code through crafted instructions. The safe_eval AST visitor rejects callable names only when they appear in a denylist, allowing any unlisted callable in attacker-controlled data to reach Python evaluation. Exploitation requires control over instructions evaluated by the control node, and resulting code runs with the Ansible process's privileges.
The record
- CVE
- CVE-2014-4678
- Published
- Feb 20, 2020
- Updated
- Aug 6, 2024
- Vendor
- Red Hat
- Product
- Ansible
- Classifications
- CWE-74, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 1.6.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo