CVE-2024-9902: Ansible-core: ansible-core user may read/write unauthorized content
Noroxi assessment
Priority: Monitor (action score 25/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- 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.
- Fixed version: azl3 ansible 2.17.0-1 on Azure Linux 3.0 2.17.11-1; azl3 ansible 2.17.11-1 on Azure Linux 3.0 2.17.11-1; cbl2 ansible 2.14.12-2 on CBL Mariner 2.0 2.14.18-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to azl3 ansible 2.17.0-1 on Azure Linux 3.0 2.17.11-1; azl3 ansible 2.17.11-1 on Azure Linux 3.0 2.17.11-1; cbl2 ansible 2.14.12-2 on CBL Mariner 2.0 2.14.18-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 6, 2024
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 16th percentile
- CWE
- CWE-863
Report tools
Action score
25
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
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
- 1.2.0-91 and laternot affected · rpm
- 3.0.1-95 and laternot affected · rpm
- 2.9.27-32 and laternot affected · rpm
- 2.12.10-54 and laternot affected · rpm
- 2.15.12-17 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
- 1:2.15.13-1.el8ap and laternot affected · rpm
- 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
- 1:2.15.13-1.el9ap and laternot affected · rpm
- 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
- 1:2.16.13-1.el8ap and laternot affected · rpm
- 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
- 1:2.16.13-1.el9ap and laternot affected · rpm
- 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.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | ansible | before 2.10.7+merged+base+2.10.17+dfsg-0+deb11u2 | 2.10.7+merged+base+2.10.17+dfsg-0+deb11u2 |
| Debian:12 | ansible | before 5.4.0-1 | 5.4.0-1 |
| Debian:12 | ansible-core | before 2.14.18-0+deb12u1 | 2.14.18-0+deb12u1 |
| Debian:13 | ansible-core | before 2.18.0-1 | 2.18.0-1 |
| openSUSE:Tumbleweed | ansible-core | before 2.17.6-1.1 | 2.17.6-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.16 | before 2.16.13-1.1 | 2.16.13-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.17 | before 2.17.6-1.1 | 2.17.6-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.18 | before 2.18.10-2.1 | 2.18.10-2.1 |
| openSUSE:Tumbleweed | ansible-core-2.19 | before 2.19.4-1.1 | 2.19.4-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.20 | before 2.20.6-1.1 | 2.20.6-1.1 |
| openSUSE:Tumbleweed | ansible-core-2.21 | before 2.21.6-1.1 | 2.21.6-1.1 |
| PyPI | ansible-core | from 2.15.0b1 · before 2.15.13rc1 | 2.15.13rc1 |
| PyPI | ansible-core | from 2.16.0b1 · before 2.16.13rc1 | 2.16.13rc1 |
| PyPI | ansible-core | from 2.17.0b1 · before 2.17.6rc1 | 2.17.6rc1 |
| PyPI | ansible-core | from 2.18.0b1 · before 2.18.0rc2 | 2.18.0rc2 |
| PyPI | ansible-core | before 2.14.18rc1 | 2.14.18rc1 |
| Red Hat:ansible_automation_platform_developer:2.4::el8 | ansible-core | before 1:2.15.13-1.el8ap | 1:2.15.13-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.4::el9 | ansible-core | before 1:2.15.13-1.el9ap | 1:2.15.13-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.5::el8 | ansible-core | before 1:2.16.13-1.el8ap | 1:2.16.13-1.el8ap |
| Red Hat:ansible_automation_platform_developer:2.5::el9 | ansible-core | before 1:2.16.13-1.el9ap | 1:2.16.13-1.el9ap |
| Red Hat:ansible_automation_platform:2.4::el8 | automation-controller-venv-tower | before 0:4.5.13-1.el8ap | 0:4.5.13-1.el8ap |
| Red Hat:ansible_automation_platform:2.4::el9 | automation-controller-venv-tower | before 0:4.5.13-1.el9ap | 0:4.5.13-1.el9ap |
| Red Hat:openstack:17.1::el9 | openstack-ansible-core | before 0:2.14.2-4.6.el9ost | 0:2.14.2-4.6.el9ost |
Same product
red hat: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-11079Ansible-core: unsafe tagging bypass via hostvars object in ansible-core22Monitor
- CVE-2024-8775Ansible-core: exposure of sensitive information in ansible vault files due to improper logging22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 ansible 2.17.0-1 on Azure Linux 3.0 | 2.17.11-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 ansible 2.17.11-1 on Azure Linux 3.0 | 2.17.11-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 ansible 2.14.12-2 on CBL Mariner 2.0 | 2.14.18-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 ansible 2.14.12-2 on CBL-Mariner 2.0 | 2.14.18-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 ansible 2.14.18-1 on CBL Mariner 2.0 | 2.14.18-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:ansible | 5.4.0-1 · Debian:12 | Package registry (OSV) |
| debian:ansible-core | 2.14.18-0+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:ansible-core | 2.17.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.16 | 2.16.13-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.17 | 2.17.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.18 | 2.18.10-2.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.19 | 2.19.4-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.20 | 2.20.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:ansible-core-2.21 | 2.21.6-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:ansible-core | 2.14.18rc1 | Package registry (OSV) |
| PyPI:ansible-core | 2.15.13rc1 | Package registry (OSV) |
| PyPI:ansible-core | 2.16.13rc1 | Package registry (OSV) |
| PyPI:ansible-core | 2.17.6rc1 | Package registry (OSV) |
| PyPI:ansible-core | 2.18.0rc2 | Package registry (OSV) |
| red hat:ansible-core | 1:2.15.13-1.el8ap · Red Hat:ansible_automation_platform_developer:2.4::el8 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.5.13-1.el8ap · Red Hat:ansible_automation_platform:2.4::el8 | Package registry (OSV) |
| red hat:openstack-ansible-core | 0:2.14.2-4.6.el9ost · Red Hat:openstack:17.1::el9 | Package 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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2026-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.
- Published
- First PoC+594 d
- TodayNov 16, 2026+740 d
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1839 · Nov 7, 2024(RedHat Ansible Güvenlik Bildirimi)
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
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 AuthorizationCVSS 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.