[llvm-bugs] Issue 3867 in oss-fuzz: llvm/clangd-fuzzer: Use-after-poison in llvm::yaml::Scanner::scanValue

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Fri Dec 8 00:14:14 PST 2017


Comment #2 on issue 3867 by ClusterFuzz-External: llvm/clangd-fuzzer:  
Use-after-poison in llvm::yaml::Scanner::scanValue
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3867#c2

ClusterFuzz has detected this issue as fixed in range  
201711160610:201712080609.

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

Project: llvm
Fuzzer: libFuzzer_llvm_clangd-fuzzer
Fuzz target binary: clangd-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Use-after-poison READ 8
Crash Address: 0x6210000029f0
Crash State:
   llvm::yaml::Scanner::scanValue
   llvm::yaml::Scanner::fetchMoreTokens
   llvm::yaml::Scanner::peekNext

Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710260448:201710270453
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201711160610:201712080609

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

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/20171208/716e4000/attachment.html>


More information about the llvm-bugs mailing list