[llvm-bugs] Issue 3409 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getCStr
monor… via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Sat Sep 16 22:03:56 PDT 2017
Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
llvm-b... at lists.llvm.org
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2017-09-17
New issue 3409 by monor... at clusterfuzz-external.iam.gserviceaccount.com:
llvm: Heap-buffer-overflow in llvm::DataExtractor::getCStr
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3409
Detailed report: https://oss-fuzz.com/testcase?key=5474306626682880
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: 0x606000000176
Crash State:
llvm::DataExtractor::getCStr
llvm::DWARFContext::dump
_start
Sanitizer: address (ASAN)
Recommended Security Severity: Medium
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201708280446:201708291805
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5474306626682880
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
more information.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any
stable releases.
* add any other useful information.
This information can help downstream consumers.
If you have questions for the OSS-Fuzz team, please file an issue at
https://github.com/google/oss-fuzz/issues.
--
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/20170916/3582af01/attachment.html>
More information about the llvm-bugs
mailing list