|gdal: Potential-null-reference in KML::startElement|
|Project Member Reported by monor...@clusterfuzz-external.iam.gserviceaccount.com, May 16||Back to list|
Detailed report: https://oss-fuzz.com/testcase?key=6562959297871872 Project: gdal Fuzzer: libFuzzer_gdal_ogr_fuzzer Fuzz target binary: ogr_fuzzer Job Type: libfuzzer_ubsan_gdal Platform Id: linux Crash Type: Potential-null-reference Crash Address: Crash State: KML::startElement doContent contentProcessor Sanitizer: undefined (UBSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_ubsan_gdal&range=201705131648:201705141650 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6562959297871872 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. This bug is subject to a 90 day disclosure deadline. If 90 days elapse without an upstream patch, then the bug report will automatically become visible to the public.
ClusterFuzz testcase 6562959297871872 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
This bug has been fixed for 30 days. It has been opened to the public. - Your friendly Sheriffbot
|► Sign in to add a comment|