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 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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2017:1599 | vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7481 | issue tracking patch vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1334 | vendor advisory |
http://www.securityfocus.com/bid/98492 | vdb entry third party advisory |
https://github.com/ansible/ansible/commit/ed56f51f185a1ffd7ea57130d260098686fcc7c2 | third party advisory patch |
https://access.redhat.com/errata/RHSA-2017:1244 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1499 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:2524 | vendor advisory |
https://access.redhat.com/errata/RHSA-2017:1476 | vendor advisory |
https://usn.ubuntu.com/4072-1/ | third party advisory vendor advisory |
https://lists.debian.org/debian-lts-announce/2021/01/msg00023.html | third party advisory mailing list |