6 matches found
Use After Free
libcurl.so is vulnerable to Use After Free. The vulnerability is due to improper freeing of an easy handle within the Curlclose function. The application frees the struct without assigning it to a null pointer. The usage of previously freed memory could lead to data corruption or lead to a crash ...
gdal:gml_geom_import_fuzzer: Heap-double-free in Curl_close
Project: https://github.com/OSGeo/gdal.git Detailed Report: https://oss-fuzz.com/testcase?key=4538384865951744 Project: gdal Fuzzing Engine: honggfuzz Fuzz Target: gmlgeomimportfuzzer Job Type: honggfuzzasangdal Platform Id: linux Crash Type: Heap-double-free Crash Address: 0x617000047580 Crash...
CVE-2018-16840
A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curlclose function, the library code first frees a struct without nulling the pointer and might then subsequently...
CVE-2018-16840
A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the "Curlclose" function, the library code first frees a struct without nulling the pointer and might then subsequently...
CURL-CVE-2018-16840 use after free in handle close
libcurl contains a heap use after free flaw in code related to closing an easy handle. When closing and cleaning up an "easy" handle in the Curlclose function, the library code first frees a struct without clearing the pointer and might then subsequently erroneously write to a struct field within...
CVE-2018-16840: Use After Free
A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curlclose function, the library code first frees a struct without nulling the pointer and might then subsequently...