Unauthenticated code execution via unsafe expression evaluation
Published Feb 20, 2020 · Updated Aug 6, 2024
Code injection in Ansible before 1.5.4 allows remote attackers to execute arbitrary code by supplying crafted instructions to safe_eval. The safe_eval function passes expressions to Python eval after relying on regular expressions to reject only module method calls and import statements, leaving other executable constructs permitted. No authentication or user interaction is required, and successful exploitation runs code with the privileges of the Ansible process.
Summary
What happened
Code injection in Ansible before 1.5.4 allows remote attackers to execute arbitrary code by supplying crafted instructions to safe_eval. The safe_eval function passes expressions to Python eval after relying on regular expressions to reject only module method calls and import statements, leaving other executable constructs permitted. No authentication or user interaction is required, and successful exploitation runs code with the privileges of the Ansible process.
The record
- CVE
- CVE-2014-4657
- Published
- Feb 20, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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