CyberSecBulletin
CVE-2023-5685NVD status: Deferred

Red Hat build of Apache Camel 4.4.0 for Spring…: Uncontrolled Resource Consumption

Published Updated By the CyberSecBulletin desk

CVE-2023-5685 is a high-severity uncontrolled resource consumption vulnerability in Red Hat build of Apache Camel 4.4.0 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 3.48% chance of exploitation within 30 days, higher than 89% 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 4.4.0 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 4.4.0 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.1 EUS for RHEL 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7Not 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 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 Data Grid 8Not 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 8Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat JBoss Fuse Service Works 6Not 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 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).

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

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

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

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.