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

monor… via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Thu Nov 9 00:17:53 PST 2017


Comment #3 on issue 3810 by  
monor... at clusterfuzz-external.iam.gserviceaccount.com:  
llvm/llvm-special-case-list-fuzzer: Heap-buffer-overflow in llvm_regcomp
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3810#c3

ClusterFuzz has detected this issue as fixed in range  
201711070608:201711090621.

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

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: 0x60a000000140
Crash State:
   llvm_regcomp
   llvm::Regex::Regex
   llvm::SpecialCaseList::Matcher::insert

Sanitizer: address (ASAN)

Recommended Security Severity: Medium

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

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

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171109/207bea35/attachment.html>


More information about the llvm-bugs mailing list