Issue metadata
Sign in to add a comment
|
Use-after-poison in base::internal::JSONParser::ConsumeStringRaw |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5699897588973568 Fuzzer: libFuzzer_base_json_reader_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Use-after-poison READ 1 Crash Address: 0x61d000001883 Crash State: base::internal::JSONParser::ConsumeStringRaw base::internal::JSONParser::ConsumeString base::internal::JSONParser::ParseToken Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=541237:541246 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5699897588973568 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Mar 8 2018
Automatically applying components based on crash stacktrace and information from OWNERS files. If this is incorrect, please apply the Test-Predator-Wrong-Components label.
,
Mar 8 2018
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/845bbd0ebcd973c78eebaa9109ba781f47b51ba3 (base_json_reader_fuzzer: Sanitizer-poison memory around the input buffer.). If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
,
Mar 8 2018
,
Mar 8 2018
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it. If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 8 2018
,
Mar 9 2018
,
Mar 13 2018
Note that this will be closed by https://chromium.googlesource.com/chromium/src/+/ab61a76223b2b14b4e3b348dae07e727be3cc2c7 and we need to wait on new repros to show up and file new bugs.
,
Mar 13 2018
ClusterFuzz has detected this issue as fixed in range 542607:542623. Detailed report: https://clusterfuzz.com/testcase?key=5699897588973568 Fuzzer: libFuzzer_base_json_reader_fuzzer Job Type: libfuzzer_chrome_asan_debug Platform Id: linux Crash Type: Use-after-poison READ 1 Crash Address: 0x61d000001883 Crash State: base::internal::JSONParser::ConsumeStringRaw base::internal::JSONParser::ConsumeString base::internal::JSONParser::ParseToken Sanitizer: address (ASAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=541237:541246 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=542607:542623 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5699897588973568 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Mar 13 2018
ClusterFuzz testcase 5699897588973568 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Mar 13 2018
,
Mar 16 2018
,
Mar 16 2018
This bug requires manual review: M66 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 16 2018
,
Mar 28 2018
,
Jun 19 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ClusterFuzz
, Mar 8 2018