[llvm-bugs] Issue 3434 in oss-fuzz: llvm: Heap-buffer-overflow in llvm::DataExtractor::getUnsigned

[monor… via monorail via llvm-bugs]

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-20

New issue 3434 by monor... at clusterfuzz-external.iam.gserviceaccount.com:  
llvm: Heap-buffer-overflow in llvm::DataExtractor::getUnsigned
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3434

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

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 4
Crash Address: 0x6100000002f6
Crash State:
   llvm::DataExtractor::getUnsigned
   llvm::FrameEntry::parseInstructions
   llvm::DWARFDebugFrame::parse

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=4760511113592832

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/20170919/545a4e79/attachment.html>