[llvm-bugs] Issue 63238 in oss-fuzz: llvm:clangd-fuzzer: Heap-buffer-overflow in llvm::raw_ostream::copy_to_buffer

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, igm... at gmail.com, sammccall at google.com, davg at google.com, mitchp at google.com, bigch... at gmail.com, eneyman at google.com, llvm-... at lists.llvm.org, jo... at devlieghere.com, jfb at chromium.org, v... at apple.com, mitch... 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-High Reported-2023-10-13
Type: Bug-Security

New issue 63238 by ClusterFuzz-External: llvm:clangd-fuzzer: Heap-buffer-overflow in llvm::raw_ostream::copy_to_buffer
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=63238

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

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

Crash Type: Heap-buffer-overflow WRITE 1
Crash Address: 0x625000004900
Crash State:
  llvm::raw_ostream::copy_to_buffer
  llvm::raw_ostream::write
  void write_unsigned_impl<unsigned int>
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

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

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

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/20231013/ba6c54aa/attachment.html>