[llvm-bugs] Issue 12429 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #6 on issue 12429 by ClusterFuzz-External:  
llvm/llvm-microsoft-demangle-fuzzer: Global-buffer-overflow in  
llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12429#c6

ClusterFuzz has detected this issue as fixed in range  
201904111857:201904120256.

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

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer
Fuzz target binary: llvm-microsoft-demangle-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Global-buffer-overflow READ 1
Crash Address: 0x00000068d68a
Crash State:
   llvm::ms_demangle::Demangler::demangleFunctionIdentifierCode
   llvm::ms_demangle::Demangler::parse
   llvm::microsoftDemangle

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904111857:201904120256

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

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.

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/20190412/6bffb800/attachment.html>