CVE-2014-4678: Ansible Code Injection Vulnerability
(updated )
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.
References
- github.com/advisories/GHSA-66c7-5pwv-mm3j
- github.com/ansible/ansible/commit/5429b85b9f6c2e640074176f36ff05fd5e4d1916
- github.com/pypa/advisory-database/tree/main/vulns/ansible/PYSEC-2020-203.yaml
- groups.google.com/forum/message/raw?msg=ansible-announce/ieV1vZvcTXU/5Q93ThkY9rIJ
- nvd.nist.gov/vuln/detail/CVE-2014-4678
- security-tracker.debian.org/tracker/CVE-2014-4678
- www.openwall.com/lists/oss-security/2014/06/26/30
- www.openwall.com/lists/oss-security/2014/07/02/2
- www.rapid7.com/db/vulnerabilities/freebsd-vid-2c493ac8-205e-11e5-a4a5-002590263bf5
- www.rapid7.com/db/vulnerabilities/gentoo-linux-cve-2014-4678
Code Behaviors & Features
Detect and mitigate CVE-2014-4678 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →