CyberSecBulletin
CVE-2024-5971NVD status: Deferred

Red Hat build of Apache Camel 3.20.7 for…: Uncontrolled Recursion

CVE-2024-5971 is a high-severity uncontrolled recursion vulnerability in Red Hat build of Apache Camel 3.20.7 for Spring Boot from Red Hat, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.92% chance of exploitation within 30 days, higher than 87% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of Red Hat build of Apache Camel 3.20.7 for Spring Boot you run against the affected versions below, and install the vendor's latest release.
  2. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatRed Hat build of Apache Camel 3.20.7 for Spring BootNot specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4.4.1 for Spring Boot 3.2Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel 4.4.2 for Spring BootNot specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application PlatformNot specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 for RHEL 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 for RHEL 9Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.4 on RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 8Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel for Spring Boot 3Not specified in the recordNot stated
Red HatRed Hat build of Apache Camel - HawtIO 4Not specified in the recordNot stated
Red HatRed Hat Build of KeycloakNot specified in the recordNot stated
Red HatRed Hat build of QuarkusNot specified in the recordNot stated
Red HatRed Hat Data Grid 8Not specified in the recordNot stated
Red HatRed Hat Fuse 7Not specified in the recordNot stated
Red HatRed Hat Integration Camel K 1Not specified in the recordNot stated
Red HatRed Hat JBoss Data Grid 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat Process Automation 7Not specified in the recordNot stated
Red HatRed Hat Single Sign-On 7Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (redhat.com).

Official description

A vulnerability was found in Undertow, where the chunked response hangs after the body was flushed. The response headers and body were sent but the client would continue waiting as Undertow does not send the expected 0\r\n termination of the chunked response. This results in uncontrolled resource consumption, leaving the server side to a denial of service attack. This happens only with Java 17 TLSv1.3 scenarios.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Recursion

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

How developers prevent this class of flaw

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

More Uncontrolled Recursion vulnerabilities (CWE-674)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Red Hat build of Apache Camel 3.20.7 for Spring Boot

All Red Hat build of Apache Camel 3.20.7 for Spring Boot vulnerabilities

Recent Uncontrolled Recursion vulnerabilities

Spotted an error? Tell us.