CVE-2023-5685VulnerabilityPublished 22 Mar 2024Updated 7 Nov 2025

CVE-2023-5685: Red Hat build of Apache Camel 4.4.0 for Spring Boot · Uncontrolled Resource Consumption

Affects Red Hat build of Apache Camel 4.4.0 for Spring BootSource CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

EPSS: 3.4% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Mar 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 2026-10-25.

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

AI-suggested

1. Apply official patches or updates from Red Hat or the Apache Camel project as soon as they become available to address the XNIO NotifierState flaw. 2. If patches are not immediately available, implement resource usage monitoring and limits on the affected applications to detect and prevent excessive growth of notifier state chains. 3. Employ runtime application self-protection (RASP) or Web Application Firewalls (WAFs) to detect anomalous patterns that could indicate attempts to exploit this vulnerability. 4. Review and harden application configurations to limit the size and complexity of asynchronous event chains or message routing paths within Apache Camel integrations. 5. Conduct thorough testing of Spring Boot applications using Apache Camel to identify potential triggers of the notifier state chain growth under load or malformed inputs. 6. Educate development and operations teams about this vulnerability to ensure rapid response and mitigation in case of suspicious activity. 7. Consider network segmentation and access controls to restrict exposure of vulnerable services to untrusted networks. 8. Maintain up-to-date inventory of affected software versions to prioritize patching and risk management efforts.

Description

A flaw was found in XNIO. The XNIO NotifierState that can cause a Stack Overflow Exception when the chain of notifier states becomes problematically large can lead to uncontrolled resource management and a possible denial of service (DoS).

Impact

For European organizations, the primary impact of CVE-2023-5685 is the potential for denial of service attacks against applications using the affected Red Hat build of Apache Camel 4.4.0 for Spring Boot. This could disrupt critical business processes, especially in sectors relying on Java-based integration frameworks such as finance, telecommunications, manufacturing, and public services. Service outages could lead to operational downtime, financial losses, and reputational damage. Since the vulnerability does not compromise data confidentiality or integrity, the risk is focused on availability. However, prolonged or repeated DoS conditions could indirectly affect compliance with service-level agreements (SLAs) and regulatory requirements for uptime and reliability. The ease of exploitation (no authentication or user interaction required) increases the threat landscape, potentially allowing remote attackers to trigger the vulnerability at scale. Organizations with automated or externally exposed integration endpoints are particularly at risk. The lack of known exploits in the wild currently reduces immediate risk but does not eliminate the need for proactive mitigation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 14 Nov 2025, 10:06 UTC

Technical details

References

Community reviews

Related threats