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

Ansible-core: ansible-core user may read/write unauthorized content

A flaw was found in Ansible. The ansible-core `user` module can allow an unprivileged user to silently create or replace the contents of any file on any system path and take ownership of it when a privileged user executes the `user` module against the unprivileged user's home directory. If the unprivileged user has traversal permissions on the directory containing the exploited target file, they retain full control over the contents of the file as its owner.

MediumCVSS 6.3 · v3.1—Proof of concept Fix available
Published
Nov 6, 2024
Updated
Jun 17, 2026
EPSS
0.3% · 16th 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

25

Monitor

Low priority for now.

CVSS
25 / 40 · 6.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · redhat
6.3
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

    • before 2.14.18rc1affected
    • 2.15.0b1 and later · before 2.15.13rc1affected
    • 2.16.0b1 and later · before 2.16.13rc1affected
    • 2.17.0b1 and later · before 2.17.6rc1affected
    • 2.18.0b1 and later · before 2.18.0rc2affected

  • Red Hat Ansible Automation Platform Execution Environments

    • 3.0.1-96 and laternot affected · rpm
    • 3.0.1-95 and laternot affected · rpm
    • 2.9.27-32 and laternot affected · rpm
    • 2.14.13-21 and laternot affected · rpm
    • 2.17.6-2 and laternot affected · rpm

  • Red Hat Red Hat Ansible Automation Platform 2.4 for RHEL 8

    • 1:2.15.13-1.el8ap and laternot affected · rpm

  • Red Hat Red Hat Ansible Automation Platform 2.4 for RHEL 9

    • 1:2.15.13-1.el9ap and laternot affected · rpm

  • Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 8

    • 1:2.16.13-1.el8ap and laternot affected · rpm

  • Red Hat Red Hat Ansible Automation Platform 2.5 for RHEL 9

    • 1:2.16.13-1.el9ap and laternot affected · rpm

  • Red Hat Red Hat Enterprise Linux 10

    • all versionsunknown

  • Red Hat Red Hat OpenStack Platform 17.1 for RHEL 9

    • 0:2.14.2-4.6.el9ost and laternot affected · rpm

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+deb11u22.10.7+merged+base+2.10.17+dfsg-0+deb11u2
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-12.18.0-1
openSUSE:Tumbleweedansible-corebefore 2.17.6-1.12.17.6-1.1
openSUSE:Tumbleweedansible-core-2.16before 2.16.13-1.12.16.13-1.1
openSUSE:Tumbleweedansible-core-2.17before 2.17.6-1.12.17.6-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.15.0b1 · before 2.15.13rc12.15.13rc1
PyPIansible-corefrom 2.16.0b1 · before 2.16.13rc12.16.13rc1
PyPIansible-corefrom 2.17.0b1 · before 2.17.6rc12.17.6rc1
PyPIansible-corefrom 2.18.0b1 · before 2.18.0rc22.18.0rc2
PyPIansible-corebefore 2.14.18rc12.14.18rc1
Red Hat:ansible_automation_platform_developer:2.4::el8ansible-corebefore 1:2.15.13-1.el8ap1:2.15.13-1.el8ap
Red Hat:ansible_automation_platform_developer:2.4::el9ansible-corebefore 1:2.15.13-1.el9ap1:2.15.13-1.el9ap
Red Hat:ansible_automation_platform_developer:2.5::el8ansible-corebefore 1:2.16.13-1.el8ap1:2.16.13-1.el8ap
Red Hat:ansible_automation_platform_developer:2.5::el9ansible-corebefore 1:2.16.13-1.el9ap1:2.16.13-1.el9ap
Red Hat:ansible_automation_platform:2.4::el8automation-controller-venv-towerbefore 0:4.5.13-1.el8ap0:4.5.13-1.el8ap
Red Hat:ansible_automation_platform:2.4::el9automation-controller-venv-towerbefore 0:4.5.13-1.el9ap0:4.5.13-1.el9ap
Red Hat:openstack:17.1::el9openstack-ansible-corebefore 0:2.14.2-4.6.el9ost0:2.14.2-4.6.el9ost

Same product

red hat: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-11079Ansible-core: unsafe tagging bypass via hostvars object in ansible-core
    22Monitor
  • 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.17.6-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.162.16.13-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:ansible-core-2.172.17.6-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.14.18rc1Package registry (OSV)
PyPI:ansible-core2.15.13rc1Package registry (OSV)
PyPI:ansible-core2.16.13rc1Package registry (OSV)
PyPI:ansible-core2.17.6rc1Package registry (OSV)
PyPI:ansible-core2.18.0rc2Package registry (OSV)
red hat:ansible-core1:2.15.13-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8Package registry (OSV)
red hat:automation-controller-venv-tower0:4.5.13-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8Package registry (OSV)
red hat:openstack-ansible-core0:2.14.2-4.6.el9ost · Red Hat:openstack:17.1::el9Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12026-06-23

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.

  1. Published
  2. First PoC+594 d
  3. TodaySep 30, 2026+694 d
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.

Credits

All researchers

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

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

  • Someone with local access to the system 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
high · data can be read
Integrity
high · data or configuration can be modified
Availability
low · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

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

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records