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

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... at gmail.com, mitchp at google.com, bigchees... at gmail.com,  
eneyman at google.com, llvm-b... at lists.llvm.org, jfb at chromium.org,  
v... at apple.com, mitchphi... at outlook.com, xpl... at gmail.com,  
akils... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-Medium  
Reported-2019-10-07
Type: Bug-Security

New issue 18061 by ClusterFuzz-External:  
llvm:llvm-special-case-list-fuzzer: Heap-buffer-overflow in p_ere
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18061

Detailed Report: https://oss-fuzz.com/testcase?key=5717405149429760

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-special-case-list-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 8
Crash Address: 0x620000003e60
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=201711070608:201711090621

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

Issue filed automatically.

See https://google.github.io/oss-fuzz/advanced-topics/reproducing for  
instructions to reproduce this bug locally.
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 need to contact the OSS-Fuzz team with a question, concern, or any  
other feedback, please file an issue at  
https://github.com/google/oss-fuzz/issues. Comments on individual Monorail  
issues are not monitored.

-- 
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/20191007/044ba580/attachment-0001.html>