New issue
Advanced search Search tips

Issue 838017 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 23
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference WRITE in void base::StringAppendVT<std::__1::basic_string<char, std::__1::char_traits<cha

Project Member Reported by ClusterFuzz, Apr 30 2018

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5058033718394880

Fuzzer: libFuzzer_base_json_string_escape_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  void base::StringAppendVT<std::__1::basic_string<char, std::__1::char_traits<cha
  base::StringAppendF
  bool base::EscapeJSONStringImpl<base::BasicStringPiece<std::__1::basic_string<ch
  
Sanitizer: undefined (UBSAN)

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5058033718394880

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.

Note: This crash might not be reproducible with the provided testcase. That said, for the past 14 days we've been seeing this crash frequently. If you are unable to reproduce this, please try a speculative fix based on the crash stacktrace in the report. The fix can be verified by looking at the crash statistics in the report, a day after the fix is deployed. We will auto-close the bug if the crash is not seen for 14 days.
 
Project Member

Comment 1 by ClusterFuzz, Apr 30 2018

Components: Internals>Core
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Cc: pnangunoori@chromium.org
Labels: Test-Predator-Wrong CF-NeedsTriage
Redo Task has been performed for regression range.
Thank You.


Project Member

Comment 3 by ClusterFuzz, Jul 23

Status: WontFix (was: Untriaged)
ClusterFuzz testcase 5058033718394880 is flaky and no longer crashes, so closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

Sign in to add a comment