Due to use of a dangling pointer, libcurl 7.29.0 through 7.71.1 can use the wrong connection when sending data.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://hackerone.com/reports/948876 | issue tracking patch exploit third party advisory |
| https://curl.haxx.se/docs/CVE-2020-8231.html | third party advisory patch |
| https://security.gentoo.org/glsa/202012-14 | third party advisory vendor advisory |
| https://www.debian.org/security/2021/dsa-4881 | third party advisory vendor advisory |
| https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E | third party advisory mailing list |
| https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E | third party advisory mailing list |
| https://www.oracle.com/security-alerts/cpuapr2022.html | third party advisory patch |
| https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf | third party advisory patch |