Skip to content
Noroxi
CVE-2017-7466· NVD / CVE Program· CNA redhat

Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems.

Ansible before version 2.3 has an input validation vulnerability in the handling of data sent from client systems. An attacker with control over a client system being managed by Ansible, and the ability to send facts back to the Ansible server, could use this flaw to execute arbitrary code on the Ansible server using the Ansible server privileges.

HighCVSS 8.0 · v3.0—No exploit Fix available
Published
Jun 22, 2018
Updated
Jun 16, 2026
EPSS
3.1% · 87th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
32 / 40 · 8.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.1%

CNA vs NVD score

NVD
8.0
CNA · redhat
8.0
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
redhatansible
redhatopenstack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat ansiblebefore 2.3
  • redhat openstack10
  • redhat openstack11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • [UNKNOWN] ansible

    • ansible 2.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12ansiblebefore 2.2.1.0-22.2.1.0-2
openSUSE:Tumbleweedansible-10before 10.6.0-1.110.6.0-1.1
openSUSE:Tumbleweedansible-11before 11.11.0-1.111.11.0-1.1
openSUSE:Tumbleweedansible-12before 12.2.0-1.112.2.0-1.1
openSUSE:Tumbleweedansible-13before 13.7.0-1.113.7.0-1.1
openSUSE:Tumbleweedansible-9before 9.8.0-1.19.8.0-1.1
PyPIansiblebefore 2.3.0.02.3.0.0
PyPIansiblebefore 2.2.3.02.2.3.0
Red Hat:openshift:3.2::el7ansiblebefore 0:2.2.3.0-1.el70:2.2.3.0-1.el7
Red Hat:openshift:3.2::el7atomic-openshift-utilsbefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.2::el7openshift-ansiblebefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.2::el7openshift-ansible-docsbefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.2::el7openshift-ansible-filter-pluginsbefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.2::el7openshift-ansible-lookup-pluginsbefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.2::el7openshift-ansible-playbooksbefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.2::el7openshift-ansible-rolesbefore 0:3.2.56-1.git.0.b844ab7.el70:3.2.56-1.git.0.b844ab7.el7
Red Hat:openshift:3.3::el7atomic-openshift-utilsbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansiblebefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansible-callback-pluginsbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansible-docsbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansible-filter-pluginsbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansible-lookup-pluginsbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansible-playbooksbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7
Red Hat:openshift:3.3::el7openshift-ansible-rolesbefore 0:3.3.82-1.git.0.af0c922.el70:3.3.82-1.git.0.af0c922.el7

+91

Other highest-scoring records for the same primary product.

  • CVE-2014-4678The safe_eval function in Ansible before 1.6.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrar
    41Plan
  • CVE-2014-4657The safe_eval function in Ansible before 1.5.4 does not properly restrict the code subset, which allows remote attackers to execute arbitrar
    40Plan
  • CVE-2014-4967Multiple argument injection vulnerabilities in Ansible before 1.6.7 allow remote attackers to execute arbitrary code by leveraging access to
    40Plan
  • CVE-2014-4966Ansible before 1.6.7 does not prevent inventory data with "{{" and "lookup" substrings, and does not prevent remote data with "{{" substring
    40Plan
  • CVE-2017-7550A flaw was found in the way Ansible (2.3.x before 2.3.3, and 2.4.x before 2.4.1) passed certain parameters to the jenkins_plugin module.
    40Plan
  • CVE-2016-8628Ansible before version 2.2.0 fails to properly sanitize fact variables sent from the Ansible controller.
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ansible2.2.1.0-2 · Debian:12Package registry (OSV)
opensuse:ansible-1010.6.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-1111.11.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-1212.2.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-1313.7.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-99.8.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:ansible2.2.3.0Package registry (OSV)
PyPI:ansible2.3.0.0Package registry (OSV)
red hat:ansible0:2.2.3.0-1.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:ansible-doc0:2.3.0.0-4.el7 · Red Hat:rhev_manager:4Package registry (OSV)
red hat:atomic-openshift-utils0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:openshift-ansible0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:openshift-ansible-callback-plugins0:3.3.82-1.git.0.af0c922.el7 · Red Hat:openshift:3.3::el7Package registry (OSV)
red hat:openshift-ansible-docs0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:openshift-ansible-filter-plugins0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:openshift-ansible-lookup-plugins0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:openshift-ansible-playbooks0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
red hat:openshift-ansible-roles0:3.2.56-1.git.0.b844ab7.el7 · Red Hat:openshift:3.2::el7Package registry (OSV)
suse:ansible2.2.3.0-5.1 · SUSE:OpenStack Cloud 7Package registry (OSV)
suse:ardana-ansible8.0+git.1596735237.54109b1-3.77.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ardana-cinder8.0+git.1596129856.263f430-3.43.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ardana-glance8.0+git.1593631779.76fa9b7-3.24.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ardana-mq8.0+git.1593618123.678c32b-3.26.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ardana-nova8.0+git.1601298847.dd01585-3.42.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:ardana-osconfig8.0+git.1595885113.93abcbc-3.49.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:documentation-hpe-helion-openstack-installation8.20201007-1.29.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:documentation-hpe-helion-openstack-operations8.20201007-1.29.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:documentation-hpe-helion-openstack-opsconsole8.20201007-1.29.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:documentation-hpe-helion-openstack-planning8.20201007-1.29.1 · SUSE:HPE Helion OpenStack 8Package registry (OSV)
suse:monasca-installer20170912_10.45-5.1 · SUSE:OpenStack Cloud 7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records