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

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

Affects Red Hat vdirsyncerSource GCVE Database

Authoritative record:CVE-2024-52304· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium · fixed in Red Hat package updates : update Red Hat vdirsyncer when convenient.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 4.0 base score

6.3Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.19.3_1, 1.16.35_1

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Nov 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

Upgrade vdirsyncer to 0.19.3_1; bzt to 1.16.35_1.

Affected software

Product	Affected	Fixed in
Homebrewvdirsyncer`pkg:brew/vdirsyncer`Other threats	Affected >=0.19.0 <0.19.3_1	Fixed in 0.19.3_1
Homebrewbzt`pkg:brew/bzt`Other threats	Affected >=1.16.2 <1.16.35_1	Fixed in 1.16.35_1

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

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: aiohttp vulnerable to request smuggling due to incorrect parsing of chunk extensions (CVE-2024-52304) 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 included: Automation controller * Fix job schedules running at incorrect times when rrule interval was set to HOURLY or MINUTELY (AAP-36572) * Fix bug where unrelated jobs could be marked as a dependency of other jobs (AAP-35309) * Include pod anti-affinity configuration on default containergroup pod spec to optimally spread workload (AAP-35055) * Updated the minor version of uWSGI to obtain updated log verbiage (AAP-33169) * automation-controller has been updated to 4.6.3 Receptor * Fixed an issue that caused a Receptor runtime panic error (AAP-36476) * receptor has been updated to 1.5.1 Container-based Ansible Automation Platform * With this update, you cannot change the postgresql_admin_username value when using a managed database node (AAP-36577) * Added update support for PCP monitoring role (AAP-36576) * With this update, ID and Image fields from a container image are used instead of Digest and ImageDigest to trigger a container update (AAP-36575) * Disabled platform gateway authentication in the proxy configuration to prevent HTTP 502 errors when the control plane is down (AAP-36484) * With this update, you can use dedicated nodes for the Redis group (AAP-36480) * Fixed an issue where disabling TLS on Automation Gateway would cause installation to fail (AAP-35966) * Fixed an issue where platform gateway uninstall would leave container systemd unit files on disk (AAP-35329) * Fixed an issue where disabling TLS on Automation Gateway proxy would cause installation to fail (AAP-35145) * With this update, you can now update the registry URL value in Event-Driven Ansible credentials (AAP-35085) * Fixed an issue where the automation hub container signing service creation failed when hub_collection_signing=false but hub_container_signing=true (AAP-34977) * Fixed an issue with the HOME environment variable for receptor containers which would cause a permission denied error on the containerized execution node (AAP-34945) * Fixed an issue where not setting up the GPG agent socket properly when multiple hub nodes are configured, resulted in not creating a GPG socket file in /var/tmp/pulp (AAP-34815) * With this update, you can now change the automation gateway port value after the initial deployment (AAP-34813) * With this update, the kernel.keys.maxkeys and kernel.keys.maxbytes settings are increased on systems with large memory configuration (AAP-34019) * Added ansible_connection=local to the inventory-growth file and clarified its usage (AAP-34016) * containerized installer setup has been updated to 2.5-6 RPM-based Ansible Automation Platform * Receptor data directory can now be configured using 'receptor_datadir' variable (AAP-36697) * Disabled platform gateway authentication in the proxy configuration to allow access to UI when the control plane is down (AAP-36667) * Fixed an issue where the metrics-utility command failed to run after updating automation controller (AAP-36486) * 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-36457) * Fixed the owner and group permissions on the /etc/tower/uwsgi.ini file (AAP-35765) * With this update, you can now update the registry URL value in Event-Driven Ansible credentials (AAP-35162) * Fixed an issue where not having eda_node_type defined in the inventory file would result in backup failure (AAP-34730) * Fixed an issue where not having routable_hostname defined in the inventory file would result in a restore failure (AAP-34563) * With this update, the inventory-growth file is now included in the ansible-automation-platform-installer (AAP-33944) * ansible-automation-platform-installer and installer setup have been updated to 2.5-6

CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
Implementation
Use a web server that employs a strict HTTP parsing procedure, such as Apache.
Implementation
Use only SSL communication.
Implementation
Terminate the client session after each request.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.5 (opens in a new tab)
Attack patterns
HTTP Response Smuggling (opens in a new tab)
HTTP Request Smuggling (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-345Insufficient Verification of Data Authenticity (opens in a new tab)
Class weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cache Poisoning (opens in a new tab)
DNS Cache Poisoning (opens in a new tab)
Spoofing of UDDI/ebXML Messages (opens in a new tab)
Application API Message Manipulation via Man-in-the-Middle (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

WeaknessesCWE-444, CWE-345

Technical details

References

Community reviews

Related threats