ansible/docs
James Cammarata a1886911fc Fixing security issue with lookup returns not tainting the jinja2 environment
CVE-2017-7481

Lookup returns wrap the result in unsafe, however when used through the
standard templar engine, this does not result in the jinja2 environment being
marked as unsafe as a whole. This means the lookup result looses the unsafe
protection and may become simple unicode strings, which can result in bad
things being re-templated.

This also adds a global lookup param and cfg options for lookups to allow
unsafe returns, so users can force the previous (insecure) behavior.

(cherry picked from commit 72dfb1570d22ac519350a8c09e76c458789120ed)
2017-05-08 11:11:47 -05:00
..
api PEP 8 indent cleanup. (#20800) 2017-01-29 07:28:53 +00:00
docsite Fixing security issue with lookup returns not tainting the jinja2 environment 2017-05-08 11:11:47 -05:00
man Add ansible-vault encrypt_string doc (#24147) 2017-05-03 12:20:39 -04:00