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

Ansible-core: exposure of sensitive information in ansible vault files due to improper logging

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: ansible (Debian:11) 2.10.7+merged+base+2.10.17+dfsg-0+deb11u2; ansible (Debian:12) 5.4.0-1; ansible-core (Debian:12) 2.14.18-0+deb12u1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to ansible (Debian:11) 2.10.7+merged+base+2.10.17+dfsg-0+deb11u2; ansible (Debian:12) 5.4.0-1; ansible-core (Debian:12) 2.14.18-0+deb12u1 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, where sensitive information stored in Ansible Vault files can be exposed in plaintext during the execution of a playbook. This occurs when using tasks such as include_vars to load vaulted variables without setting the no_log: true parameter, resulting in sensitive data being printed in the playbook output or logs. This can lead to the unintentional disclosure of secrets like passwords or API keys, compromising security and potentially allowing unauthorized access or actions.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Sep 13, 2024
Updated
Sep 17, 2026
EPSS
0.2% · 18th percentile

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.2%

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-8775

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for red hat records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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

    • 1.0.0 and later · up to and including 2.17.4affected · semver

  • 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 Discovery 1 for RHEL 9

    • 1.12.0-1 and laternot affected · rpm
    • 1.12.0-1 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 versionsaffected

  • Red Hat Red Hat Enterprise Linux 8

    • all versionsaffected

  • Red Hat Red Hat Enterprise Linux 9

    • all versionsunknown

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

    • 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+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.17.5-52.17.5-5
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.17.0b1 · before 2.17.62.17.6
PyPIansible-corebefore 2.16.132.16.13
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
SUSE:Manager Client Tools 15ansiblebefore 2.9.27-150000.1.20.12.9.27-150000.1.20.1
SUSE:Manager Client Tools 15ansiblebefore 2.9.27-150000.1.20.12.9.27-150000.1.20.1
SUSE:Manager Client Tools 15spacewalk-client-toolsbefore 4.3.22-150000.3.100.14.3.22-150000.3.100.1
SUSE:Manager Client Tools 15spacewalk-client-toolsbefore 4.3.22-150000.3.100.14.3.22-150000.3.100.1
SUSE:Manager Client Tools 15uyuni-proxy-systemd-servicesbefore 4.3.15-150000.1.30.14.3.15-150000.1.30.1
SUSE:Manager Client Tools 15uyuni-proxy-systemd-servicesbefore 4.3.15-150000.1.30.14.3.15-150000.1.30.1

Same product

red hat: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-9902Ansible-core: ansible-core user may read/write unauthorized content
    25Monitor
  • CVE-2024-11079Ansible-core: unsafe tagging bypass via hostvars object in ansible-core
    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:ansible2.9.27-150000.1.20.1 · openSUSE:Leap 15.6Package 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.16.13Package registry (OSV)
PyPI:ansible-core2.17.6Package 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)
suse:ansible2.9.27-150000.1.20.1 · SUSE:Manager Client Tools 15Package registry (OSV)
suse:spacewalk-client-tools4.3.22-150000.3.100.1 · SUSE:Manager Client Tools 15Package registry (OSV)
suse:uyuni-proxy-systemd-services4.3.15-150000.1.30.1 · SUSE:Manager Client Tools 15Package 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.

Credits

All researchers

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-532 · Insertion of Sensitive Information into Log File

CVSS vector

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

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.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records