[llvm-bugs] Issue 5953 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::raw_svector_ostream::write_impl

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #2 on issue 5953 by ClusterFuzz-External:  
llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in  
llvm::raw_svector_ostream::write_impl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5953#c2

ClusterFuzz has detected this issue as fixed in range  
201802220624:201802230625.

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

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 {*}
Crash Address: 0x606000000111
Crash State:
   llvm::raw_svector_ostream::write_impl
   llvm::raw_ostream::write
   llvm::Twine::printOneChild

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=201802220624:201802230625

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

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/20180223/8244fc8e/attachment.html>