[llvm-bugs] Issue 3892 in oss-fuzz: llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere

monor… via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Sun Oct 29 03:47:33 PDT 2017


Status: New
Owner: ----
CC: kcc at google.com,  mascasa at google.com,  jdevlieg... at apple.com,   
llvm-b... at lists.llvm.org,  v... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-10-29

New issue 3892 by monor... at clusterfuzz-external.iam.gserviceaccount.com:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3892

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

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-special-case-list-fuzzer
Fuzz target binary: llvm-special-case-list-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 8
Crash Address: 0x6150000004d8
Crash State:
   p_ere
   p_ere
   p_ere

Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451

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

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/20171029/15a76104/attachment.html>


More information about the llvm-bugs mailing list