[llvm-bugs] Issue 3417 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getU32

monor… via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Tue Oct 24 00:08:28 PDT 2017


Comment #3 on issue 3417 by  
monor... at clusterfuzz-external.iam.gserviceaccount.com: llvm:  
Heap-buffer-overflow in llvm::DataExtractor::getU32
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3417#c3

ClusterFuzz has detected this issue as fixed in range  
201710230449:201710240446.

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

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: 0x61a000000b59
Crash State:
   llvm::DataExtractor::getU32
   llvm::DWARFUnit::extractImpl
   llvm::DWARFUnit::extract

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=201710230449:201710240446

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

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/20171024/e892b1f6/attachment.html>


More information about the llvm-bugs mailing list