gdal/cad_fuzzer: Crash in _int_malloc

2017-10-30T12:48:21
ID OSSFUZZ-3929
Type ossfuzz
Reporter Google
Modified 2018-02-08T23:58:42

Description

Detailed report: https://oss-fuzz.com/testcase?key=5401392446439424

Project: gdal Fuzzer: libFuzzer_gdal_cad_fuzzer Fuzz target binary: cad_fuzzer Job Type: libfuzzer_ubsan_gdal Platform Id: linux

Crash Type: UNKNOWN READ Crash Address: 0x7f9803eeb880 Crash State: _int_malloc std::__1::basic_filebuf<char, std::__1::char_traits<char> >::setbuf std::__1::basic_filebuf<char, std::__1::char_traits<char> >::basic_filebuf

Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5401392446439424

Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information.

<b>Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.</b>

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.

When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers.

If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues.