VDB

CVE-2017-7481

CVE-2017-7481 PUBLISHED CVSS 5.3 MEDIUM

Ansible fails to properly mark lookup-plugin results as unsafe

Reported by redhat · Published July 19, 2018

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
ansibleUbuntu:16.04:LTS2.0.0.2-2ubuntu1.3
ansible_engineredhat2.4.0.0, 2.3.1.0

Risk scores

CVSS 3.0
5.3
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N

Affected products

VendorProductVersions
[UNKNOWN]ansibleansible 2.3.1.0, ansible 2.4.0.0
[UNKNOWN]ansible2.3.1.0, 2.4.0.0
PyPIansible2.3.0.0, 0, 2.2.0.0

Timeline

  • May 17, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Mar 6, 2026 Distribution Patch (7 in total, the first dated here)
  • Mar 6, 2026 Security Advisory (11 in total, the first dated here)
  • Sep 20, 2026 CVE Updated
  • Sep 28, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-7481
vulnetix vdb fixes CVE-2017-7481

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-7481/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›