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.
AI analysis not yet available
Plain-English explanation, risk summary, and remediation steps will appear here once AI analysis is complete.
No Fix Known
No patch has been released yet. Apply workarounds or mitigations where available.
Published
CVE disclosed publicly
Last Modified
Most recent update
Indexed to CVEInsight
Added to this platform
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
12
Affected Products
6
References
haxx / libcurl
| - |
| netapp | clustered_data_ontap | - | - |
| broadcom | brocade_fabric_operating_system_firmware | - | - |
| netapp | h300s_firmware | - | - |
| netapp | h500s_firmware | - | - |
| netapp | h700s_firmware | - | - |
| netapp | h410s_firmware | - | - |
| splunk | universal_forwarder | 8.2.0 - 8.2.12 | - |
| splunk | universal_forwarder | 9.0.0 - 9.0.6 | - |
| splunk | universal_forwarder | - | - |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploitability
Impact