[llvm-bugs] Issue 24790 in oss-fuzz: llvm:clang-objc-fuzzer: Heap-buffer-overflow in clang::Lexer::getTokenPrefixLength

[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, davg at google.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-2020-08-10
Type: Bug-Security

New issue 24790 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Heap-buffer-overflow in clang::Lexer::getTokenPrefixLength
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=24790

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

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: clang-objc-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x7fd2d09dff07
Crash State:
  clang::Lexer::getTokenPrefixLength
  clang::StringLiteralParser::CopyStringFragment
  clang::StringLiteralParser::init
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

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

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

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/20200809/5e4e9659/attachment.html>