A double free vulnerability exists in libcurl <8.0.0 when sharing HSTS data between separate "handles". This sharing was introduced without considerations for do this sharing across separate threads but there was no indication of this fact in the documentation. Due to missing mutexes or thread locks, two threads sharing the same HSTS data could end up doing a double-free or use-after-free.
References
Link | Resource |
---|---|
https://hackerone.com/reports/1897203 | Exploit Third Party Advisory |
https://security.gentoo.org/glsa/202310-12 | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20230420-0010/ | Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
AND |
|
Configuration 4 (hide)
AND |
|
Configuration 5 (hide)
AND |
|
Configuration 6 (hide)
AND |
|
Configuration 7 (hide)
|
History
No history.
Information
Published : 2023-03-30 20:15
Updated : 2024-03-27 14:46
NVD link : CVE-2023-27537
Mitre link : CVE-2023-27537
CVE.ORG link : CVE-2023-27537
JSON object : View
Products Affected
splunk
- universal_forwarder
netapp
- h300s_firmware
- h410s_firmware
- clustered_data_ontap
- active_iq_unified_manager
- h500s_firmware
- h500s
- h700s_firmware
- h300s
- h700s
- h410s
broadcom
- brocade_fabric_operating_system_firmware
haxx
- libcurl
CWE
CWE-415
Double Free