Ansible fails to properly mark lookup-plugin results as unsafe
Ansible before versions 2.1.6.0, 2.2.3.0, 2.3.1.0, and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-7481US | critical9.8 | — | ||
Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Un… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2017:1244WEB
- https://access.redhat.com/errata/RHSA-2017:1334WEB
- https://access.redhat.com/errata/RHSA-2017:1476WEB
- https://access.redhat.com/errata/RHSA-2017:1499WEB
- https://access.redhat.com/errata/RHSA-2017:1599WEB
- https://access.redhat.com/errata/RHSA-2017:2524WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7481WEB
- https://github.com/ansible/ansiblePACKAGE
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan