Ansible fails to properly mark lookup-plugin results as unsafe
[UNKNOWN] ansible
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
[UNKNOWN] ansible
| Product | Affected | Fixed in |
|---|---|---|
| ansible PyPI |
|
|
2.4.0.0Ansible 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 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.
From the CVE record · redhat
Affected Ansible versions do not properly mark lookup-plugin results as unsafe. An attacker who controls the results of lookup() calls could inject Unicode strings that Jinja2 parses, resulting in code execution. The input does not specify whether this requires network or local access, authentication, or user interaction.
Engineers running the PyPI ansible package in the listed affected ranges should check their installations.