CVE-2014-4657
Published: 20 February 2020
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.
Priority
Status
Package | Release | Status |
---|---|---|
ansible Launchpad, Ubuntu, Debian |
artful |
Not vulnerable
(1.6.5+dfsg-1)
|
bionic |
Not vulnerable
(1.6.5+dfsg-1)
|
|
cosmic |
Not vulnerable
(1.6.5+dfsg-1)
|
|
disco |
Not vulnerable
(1.6.5+dfsg-1)
|
|
lucid |
Does not exist
|
|
precise |
Does not exist
|
|
saucy |
Ignored
(end of life)
|
|
trusty |
Not vulnerable
(1.5.4+dfsg-1)
|
|
upstream |
Released
(1.5.5+dfsg-1)
|
|
utopic |
Not vulnerable
(1.6.5+dfsg-1)
|
|
vivid |
Not vulnerable
(1.6.5+dfsg-1)
|
|
wily |
Not vulnerable
(1.6.5+dfsg-1)
|
|
xenial |
Not vulnerable
(1.6.5+dfsg-1)
|
|
yakkety |
Not vulnerable
(1.6.5+dfsg-1)
|
|
zesty |
Not vulnerable
(1.6.5+dfsg-1)
|
|
Patches: upstream: https://github.com/ansible/ansible/commit/998793fd0ab55705d57527a38cee5e83f535974c |
Severity score breakdown
Parameter | Value |
---|---|
Base score | 9.8 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | None |
User interaction | None |
Scope | Unchanged |
Confidentiality | High |
Integrity impact | High |
Availability impact | High |
Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |