CVE-2024-57699VulnerabilityPublished 2 Apr 2025Updated 5 Nov 2026

Red Hat Security Advisory: Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 update is now available (RHBQ 3.15.4.GA)

Affects Red HatSource GCVE Database

Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 5 Nov 2026, 13:36 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

AI-suggested

Red Hat recommends applying the update to Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 (RHBQ 3.15.4.GA) to address this vulnerability. Before updating, back up all relevant data including applications, configuration files, and databases. No other mitigation is currently recommended by Red Hat. Monitor the vendor advisory for further updates or additional fixes.

Description

A security update is available for Red Hat Build of Apache Camel 4.8 for Quarkus 3.15 (RHBQ 3.15.4.GA) addressing a potential denial of service (DoS) vulnerability via stack exhaustion in the json-smart library (CVE-2024-57699). This issue is due to an incomplete fix for a previous vulnerability (CVE-2023-1370) affecting json-smart versions 2.5.0 through 2.5.1. The advisory also references SmallRye Fault Tolerance vulnerabilities (CVE-2025-2240) in related components. The DoS vulnerability can cause application crashes by exhausting stack memory when processing specially crafted JSON input. Red Hat rates the security impact as Important and recommends applying the update to improve security and stability.

Impact

The vulnerability can cause denial of service through stack exhaustion when processing malicious JSON input, potentially crashing the application or causing it to exit unexpectedly. This impacts availability but does not affect confidentiality or integrity. The issue exists due to an incomplete prior fix, affecting json-smart versions 2.5.0 through 2.5.1. Red Hat rates the security impact as Important (high availability impact). There is no indication of active exploitation in the wild.

CWE-674Uncontrolled Recursion (opens in a new tab)
Class weakness
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
Implementation
Ensure that an end condition will be reached under all logic conditions. The end condition may include checking against the depth of recursion and exiting with an error if the recursion goes too deep. The complexity of the end condition contributes to the effectiveness of this action.
Implementation
Increase the stack size.
Attack patterns
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1325Improperly Controlled Sequential Memory Allocation (opens in a new tab)
Base weakness
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
Implementation
Ensure multiple allocations of the same kind of object are properly tracked - possibly across multiple sessions, requests, or messages. Define an appropriate strategy for handling requests that exceed the limit, and consider supporting a configuration option so that the administrator can extend the amount of memory to…
Operation
Run the program using system-provided resource limits for memory. This might still cause the program to crash or exit, but the impact to the rest of the system will be minimized.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
Excessive Allocation (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

Description

AI analysisMachine-generated, updated 5 Nov 2026, 13:36 UTC

WeaknessesCWE-674, CWE-1325

Technical details

References

Community reviews

Related threats