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.
The product calls free() twice on the same memory address.
| Link | Tags |
|---|---|
| https://hackerone.com/reports/1897203 | third party advisory exploit |
| https://security.netapp.com/advisory/ntap-20230420-0010/ | third party advisory |
| https://security.gentoo.org/glsa/202310-12 | third party advisory vendor advisory |