CVE-2024-8775VulnerabilityPublished 3 Dec 2024Updated 22 Oct 2026

Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.4 Product Security and Bug Fix Update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

Authoritative record:CVE-2024-8775· Medium 5.5

Not known to be exploited · CVSS 5.5 Medium · fixed in Red Hat Ansible Automation Platform 2.4 for RHEL 8 package updates : update Red Hat ansible-core when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.4

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
ansible-core	Affected >=1.0.0 <=2.17.4	Fixed in–
GitHubansible-core`pkg:github/ansible-core`Other threats	Affected >=1.0.0 <=2.17.4	Fixed in–
GitHubansible/ansible`pkg:github/ansible/ansible`Other threats	Affected =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released an official product update (version 2.4-8) that addresses these vulnerabilities and includes additional bug fixes. Users of Red Hat Ansible Automation Platform 2.4 should upgrade to version 2.4-8 or later. Note that the 2.4-8 installer can only restore backups created with 2.4-8 or later, so backups should be made before and after the upgrade. No other specific mitigations are indicated by the vendor advisory.

Description

Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to individual teams, while automation developers retain the freedom to write tasks that leverage existing knowledge without the overhead. Ansible Automation Platform makes it possible for users across an organization to share, vet, and manage automation content by means of a simple, powerful, and agentless language. Security Fix(es): * automation-controller: dompurify: XSS vulnerability via prototype pollution (CVE-2024-45801) * automation-controller: path-to-regexp: Backtracking regular expressions cause ReDoS (CVE-2024-45296) * ansible-core: Exposure of Sensitive Information in Ansible Vault Files Due to Improper Logging (CVE-2024-8775) * ansible-core: ansible-core user may read/write unauthorized content (CVE-2024-9902) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section. Updates and fixes for automation controller: * Fix job schedules running at incorrect times when rrule interval was set to HOURLY or MINUTELY (AAP-36573) * Fixed an issue where sensitive data was displayed in the job output (AAP-35582) * With this update, you can now save a constructed inventory when verbosity is greater than 2 (AAP-35570) * Fix bug where unrelated jobs could be marked as a dependency of other jobs (AAP-35310) * Add support for receiving webhooks from Bitbucket Data Center, and add support for posting build statuses back (AAP-35013) * Notification List no longer errors when notifications have a missing or null organization field (AAP-34051) * Fixed an issue where Thycotic secret server credentials form fields were mis-matched (AAP-31236) * automation-controller has been updated to 4.5.13 Updates and fixes for receptor: * Fixed an issue that caused a Receptor runtime panic error (AAP-36477) * receptor has been updated to 1.5.1 Updates and fixes for installer and setup: * Receptor data directory can now be configured using 'receptor_datadir' variable (AAP-36699) * Fixed issue where metrics-utility command failed to run after updating Automation controller (AAP-36567) * Fix issue where the dispatcher service went into FATAL status and failed to process new jobs after a database outage of a few minutes (AAP-36456) * Fixed an issue that caused incorrect IDs for RBAC in the database following a backup restore (AAP-35311) * With this update, installer tasks that include CA or key information are obfuscated (AAP-27480) * installer and setup have been updated to 2.4-8 Note: The 2.4-8 installer can restore a backup created with 2.4-8 or later only. Ensure that you make a backup before and after the upgrade to 2.4-8 or later.

Impact

The vulnerabilities could allow attackers to execute cross-site scripting attacks, cause denial of service through regular expression backtracking, expose sensitive information stored in Ansible Vault files, and enable unauthorized read/write operations by the ansible-core user. These issues could compromise the confidentiality and integrity of automation tasks and data managed by the platform. The overall security impact is rated moderate by Red Hat.

Summary

The Red Hat Ansible Automation Platform 2.4 update addresses four security vulnerabilities: CVE-2024-45801 (XSS via prototype pollution in dompurify), CVE-2024-45296 (ReDoS due to backtracking regex in path-to-regexp), CVE-2024-8775 (exposure of sensitive information in Ansible Vault files due to improper logging), and CVE-2024-9902 (ansible-core user may read/write unauthorized content). The advisory includes fixes for these vulnerabilities along with other bug fixes in automation-controller, receptor, and installer components. The update is available in version 2.4-8 and later. The vendor rates the security impact as moderate and recommends upgrading to the fixed versions.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1333Inefficient Regular Expression Complexity (opens in a new tab)
Base weaknessLikelihood of exploit: High
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
Architecture and Design
Use regular expressions that do not support backtracking, e.g. by removing nested quantifiers.
System Configuration
Set backtracking limits in the configuration of the regular expression implementation, such as PHP's pcre.backtrack_limit. Also consider limits on execution time for the process.
Implementation
Do not use regular expressions with untrusted input. If regular expressions must be used, avoid using backtracking in the expression.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
Regular Expression Exponential Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Aug 2026, 20:15 UTC

WeaknessesCWE-532, CWE-863, CWE-1333

Technical details

References

Community reviews

Related threats