[llvm-bugs] Issue 3653 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::identify_magic
monor… via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Thu Oct 19 00:09:53 PDT 2017
Comment #2 on issue 3653 by
monor... at clusterfuzz-external.iam.gserviceaccount.com:
llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::identify_magic
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3653#c2
ClusterFuzz has detected this issue as fixed in range
201710160455:201710190451.
Detailed report: https://oss-fuzz.com/testcase?key=6095520196984832
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer
Fuzz target binary: llvm-dwarfdump-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Heap-buffer-overflow READ 4
Crash Address: 0x60c000000240
Crash State:
llvm::identify_magic
llvm::object::ObjectFile::createObjectFile
_start
Sanitizer: address (ASAN)
Recommended Security Severity: Medium
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201708280446:201708291805
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=6095520196984832
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
more information.
If you suspect that the result above is incorrect, try re-doing that job on
the test case report page.
--
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings
Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171019/f8dd95db/attachment-0001.html>
More information about the llvm-bugs
mailing list