[llvm-bugs] Issue 3616 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::StringMapImpl::FindKey

[monor… via monorail via llvm-bugs]

Comment #2 on issue 3616 by  
monor... at clusterfuzz-external.iam.gserviceaccount.com: llvm:  
Heap-buffer-overflow in llvm::StringMapImpl::FindKey
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3616#c2

ClusterFuzz has detected this issue as fixed in range  
201710121744:201710130152.

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

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 1
Crash Address: 0x6120000008ea
Crash State:
   llvm::StringMapImpl::FindKey
   llvm::object::WasmObjectFile::parseLinkingSection
   llvm::object::WasmObjectFile::parseCustomSection

Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201709150442:201710101928
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710121744:201710130152

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

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/20171013/6a9e14ab/attachment.html>