CVE Vulnerabilities

CVE-2024-2398

Missing Release of Resource after Effective Lifetime

Published: Mar 27, 2024 | Modified: Jul 30, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

NameVendorStart VersionEnd Version
CurlHaxx7.44.0 (including)8.7.0 (excluding)
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-curl-0:8.7.1-2.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-httpd-0:2.4.57-10.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-mod_http2-0:1.15.19-37.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-mod_jk-0:1.2.49-6.redhat_1.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-mod_md-1:2.4.24-6.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-mod_proxy_cluster-0:1.3.20-4.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-mod_security-0:2.9.3-36.el8jbcs*
JBoss Core Services for RHEL 8RedHatjbcs-httpd24-nghttp2-0:1.43.0-13.el8jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-curl-0:8.7.1-2.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-httpd-0:2.4.57-10.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-mod_http2-0:1.15.19-37.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-mod_jk-0:1.2.49-6.redhat_1.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-mod_md-1:2.4.24-6.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-mod_proxy_cluster-0:1.3.20-4.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-mod_security-0:2.9.3-36.el7jbcs*
JBoss Core Services on RHEL 7RedHatjbcs-httpd24-nghttp2-0:1.43.0-13.el7jbcs*
Red Hat Enterprise Linux 8RedHatcurl-0:7.61.1-34.el8_10.2*
Red Hat Enterprise Linux 9RedHatcurl-0:7.76.1-29.el9_4.1*
Red Hat Enterprise Linux 9RedHatcurl-0:7.76.1-29.el9_4.1*
Red Hat Enterprise Linux 9.2 Extended Update SupportRedHatcurl-0:7.76.1-23.el9_2.7*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-config-sync-rhel9:1.4.7-3*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-flow-collector-rhel9:1.4.7-3*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-operator-bundle:1.4.7-4*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-router-rhel9:2.4.3-7*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-service-controller-rhel9:1.4.7-3*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-site-controller-rhel9:1.4.7-3*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-config-sync-rhel9:1.4.7-2*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-flow-collector-rhel9:1.4.7-2*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-operator-bundle:1.4.7-2*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-router-rhel9:2.4.3-6*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-service-controller-rhel9:1.4.7-2*
Service Interconnect 1.4 for RHEL 9RedHatservice-interconnect/skupper-site-controller-rhel9:1.4.7-2*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-config-sync-rhel9:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-controller-podman-container-rhel9:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-controller-podman-rhel9:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-flow-collector-rhel9:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-operator-bundle:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-router-rhel9:2.5.3-6*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-service-controller-rhel9:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-site-controller-rhel9:1.5.5-4*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-config-sync-rhel9:1.5.5-3*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-controller-podman-container-rhel9:1.5.5-3*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-controller-podman-rhel9:1.5.5-3*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-flow-collector-rhel9:1.5.5-3*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-operator-bundle:1.5.5-3*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-router-rhel9:2.5.3-5*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-service-controller-rhel9:1.5.5-3*
Service Interconnect 1 for RHEL 9RedHatservice-interconnect/skupper-site-controller-rhel9:1.5.5-3*
Text-Only JBCSRedHatjbcs-httpd24-curl*
CurlUbuntudevel*
CurlUbuntuesm-infra/bionic*
CurlUbuntuesm-infra/focal*
CurlUbuntuesm-infra/xenial*
CurlUbuntufocal*
CurlUbuntujammy*
CurlUbuntumantic*
CurlUbuntunoble*
CurlUbuntuoracular*
CurlUbuntuplucky*
CurlUbuntuquesting*
CurlUbuntuupstream*

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References