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.
References
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Configuration 4 (hide)
|
Configuration 5 (hide)
| AND |
|
Configuration 6 (hide)
| AND |
|
Configuration 7 (hide)
| AND |
|
Configuration 8 (hide)
| AND |
|
Configuration 9 (hide)
| AND |
|
Configuration 10 (hide)
| AND |
|
Configuration 11 (hide)
| AND |
|
Configuration 12 (hide)
| AND |
|
History
No history.
Information
Published : 2024-03-27 08:15
Updated : 2025-07-30 19:42
NVD link : CVE-2024-2398
Mitre link : CVE-2024-2398
CVE.ORG link : CVE-2024-2398
JSON object : View
Products Affected
netapp
- h615c_firmware
- brocade_fabric_operating_system
- ontap_select_deploy_administration_utility
- h700s_firmware
- h410s
- h500s_firmware
- h610c_firmware
- h610s
- h610s_firmware
- h500s
- h410s_firmware
- bootstrap_os
- active_iq_unified_manager
- h615c
- h300s
- hci_compute_node
- h300s_firmware
- h700s
- h610c
haxx
- curl
apple
- macos
fedoraproject
- fedora
CWE
CWE-772
Missing Release of Resource after Effective Lifetime
