Skip to content
Noroxi
CVE-2024-11079· NVD / CVE Program· CNA redhat

Ansible-core: unsafe tagging bypass via hostvars object in ansible-core

A flaw was found in Ansible-Core. This vulnerability allows attackers to bypass unsafe content protections using the hostvars object to reference and execute templated content. This issue can lead to arbitrary code execution if remote data or module outputs are improperly templated within playbooks.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Nov 11, 2024
Updated
Jun 29, 2026
EPSS
0.5% · 40th 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

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
5.5
NVD has not scored this yet; the score shown is the CNA’s.

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

Affected systems

—

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.

  • github.com/ansible/ansible ansible-core

    • up to and including 2.18.0affected · semver
  • Red Hat Ansible Automation Platform Execution Environments

    • 1.2.0-93 and laternot affected · rpm
    • 3.0.1-108 and laternot affected · rpm
    • 2.9.27-34 and laternot affected · rpm
    • 2.12.10-56 and laternot affected · rpm
    • 2.15.13-4 and laternot affected · rpm
  • Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8

    • 1:2.16.14-1.el8ap and laternot affected · rpm
  • Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9

    • 1:2.16.14-1.el9ap and laternot affected · rpm
  • Red Hat Red Hat Enterprise Linux 10

    • all versionsunknown
  • Red Hat Red Hat Enterprise Linux AI (RHEL AI)

    • all versionsaffected
    • all versionsaffected

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11ansiblebefore 2.10.7+merged+base+2.10.17+dfsg-0+deb11u42.10.7+merged+base+2.10.17+dfsg-0+deb11u4
Debian:12ansiblebefore 5.4.0-15.4.0-1
Debian:12ansible-corebefore 2.14.18-0+deb12u12.14.18-0+deb12u1
Debian:13ansible-corebefore 2.18.0-22.18.0-2
openSUSE:Tumbleweedansible-corebefore 2.18.1-1.12.18.1-1.1
openSUSE:Tumbleweedansible-core-2.16before 2.16.14-1.12.16.14-1.1
openSUSE:Tumbleweedansible-core-2.17before 2.17.7-1.12.17.7-1.1
openSUSE:Tumbleweedansible-core-2.18before 2.18.10-2.12.18.10-2.1
openSUSE:Tumbleweedansible-core-2.19before 2.19.4-1.12.19.4-1.1
openSUSE:Tumbleweedansible-core-2.20before 2.20.6-1.12.20.6-1.1
PyPIansible-corefrom 2.17.0b1 · before 2.17.7rc12.17.7rc1
PyPIansible-corefrom 2.18.0b1 · before 2.18.1rc12.18.1rc1
PyPIansible-corebefore 2.16.14rc12.16.14rc1
Red Hat:ansible_automation_platform_developer:2.5::el8ansible-corebefore 1:2.16.14-1.el8ap1:2.16.14-1.el8ap
Red Hat:ansible_automation_platform_developer:2.5::el9ansible-corebefore 1:2.16.14-1.el9ap1:2.16.14-1.el9ap
Red Hat:ansible_automation_platform:2.5::el8automation-gateway-serverbefore 0:2.5.20241218-1.el8ap0:2.5.20241218-1.el8ap
Red Hat:ansible_automation_platform:2.5::el9automation-gateway-serverbefore 0:2.5.20241218-1.el9ap0:2.5.20241218-1.el9ap

Other highest-scoring records for the same primary product.

  • CVE-2024-9902Ansible-core: ansible-core user may read/write unauthorized content
    25Monitor
  • CVE-2024-8775Ansible-core: exposure of sensitive information in ansible vault files due to improper logging
    22Monitor

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:ansible5.4.0-1 · Debian:12Package registry (OSV)
debian:ansible-core2.14.18-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:ansible-core2.18.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.162.16.14-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.172.17.7-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.182.18.10-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.192.19.4-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.202.20.6-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:ansible-core2.16.14rc1Package registry (OSV)
PyPI:ansible-core2.17.7rc1Package registry (OSV)
PyPI:ansible-core2.18.1rc1Package registry (OSV)
red hat:ansible-core1:2.16.14-1.el8ap · Red Hat:ansible_automation_platform_developer:2.5::el8Package registry (OSV)
red hat:automation-gateway-server0:2.5.20241218-1.el8ap · Red Hat:ansible_automation_platform:2.5::el8Package 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.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
low · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality impact
Low
Integrity impact
Low
Availability impact
Low

CVSS vector

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

nvd-secondary

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