Comment #3 on issue 14247 by ClusterFuzz-External:
llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in
llvm::ms_demangle::Node**
llvm::ms_demangle::ArenaAllocator::allocArray<llvm::ms
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14247#c3
ClusterFuzz has detected this issue as fixed in range
201904160252:201904180259.
Detailed report: https://oss-fuzz.com/testcase?key=5105728374702080
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: Heap-buffer-overflow WRITE {*}
Crash Address: 0x6210000bc900
Crash State:
llvm::ms_demangle::Node**
llvm::ms_demangle::ArenaAllocator::allocArray<llvm::ms
llvm::ms_demangle::Demangler::demangleNameScopeChain
llvm::ms_demangle::Demangler::demangleMemberPointerType
Sanitizer: address (ASAN)
Recommended Security Severity: High
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901070410:201901080410
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201904160252:201904180259
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5105728374702080
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.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
