go-dns:fuzz_msg_unpack: Crash with empty stacktrace

Type ossfuzz
Reporter Google
Modified 2020-09-25T20:07:45


Detailed Report: https://oss-fuzz.com/testcase?key=5642061701971968

Project: go-dns Fuzzing Engine: libFuzzer Fuzz Target: fuzz_msg_unpack Job Type: libfuzzer_asan_go-dns Platform Id: linux

Crash Type: UNKNOWN READ Crash Address: 0x00000002d140 Crash State: NULL Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Crash Revision: https://oss-fuzz.com/revisions?job=libfuzzer_asan_go-dns&revision=202007260252

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

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.

**** UNREPRODUCIBLE **** 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.

It may be possible to reproduce by trying the following options: - Run testcase multiple times for a longer duration. - Run fuzzing without testcase argument to hit the same crash signature.

If it still does not reproduce, try a speculative fix based on the crash stacktrace and verify if it works by looking at the crash statistics in the report. We will auto-close the bug if the crash is not seen for 14 days.

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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, please file an issue at https://github.com/google/oss-fuzz/issues. Comments on individual Monorail issues are not monitored.

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.