A use after free vulnerability exists in curl <v8.1.0 in the way libcurl offers a feature to verify an SSH server's public key using a SHA 256 hash. When this check fails, libcurl would free the memory for the fingerprint before it returns an error message containing the (now freed) hash. This flaw risks inserting sensitive heap-based data into the error message that might be shown to users or otherwise get leaked and revealed.
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/1913733 | patch third party advisory exploit |
| https://security.netapp.com/advisory/ntap-20230609-0009/ | third party advisory |
| https://support.apple.com/kb/HT213843 | third party advisory |
| https://support.apple.com/kb/HT213844 | third party advisory |
| https://support.apple.com/kb/HT213845 | third party advisory |
| http://seclists.org/fulldisclosure/2023/Jul/52 | third party advisory mailing list |
| http://seclists.org/fulldisclosure/2023/Jul/48 | third party advisory mailing list |
| http://seclists.org/fulldisclosure/2023/Jul/47 | third party advisory mailing list |
| https://security.gentoo.org/glsa/202310-12 | third party advisory vendor advisory |