Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.

Seems likely to be a dupe of  Issue 792306 . Eric?

Actually, while the regression comes from the same CL, it appears to be in a different function. The patch for 792306 might avoid the crash for this specific fuzzed-input, but adding another digit at the end seems likely to trigger the same crash.

   o{color:rgb(0

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

https://chromium-review.googlesource.com/c/chromium/src/+/821793

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fcb44ac06933a5f1300db5c0677ffe2a07a569ac

commit fcb44ac06933a5f1300db5c0677ffe2a07a569ac
Author: Eric Willigers <ericwilligers@chromium.org>
Date: Tue Dec 12 08:41:21 2017

CSS Parser: Detect incomplete rgba colors

args.Peek() - 1  is only valid if we are not at the end (or beginning)
of the token stream.

BUG= 792464 

Change-Id: I1a475ce873723877d6bbb9d7b24c3773dd1090ee
Reviewed-on: https://chromium-review.googlesource.com/821793
Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523375}
[modify] https://crrev.com/fcb44ac06933a5f1300db5c0677ffe2a07a569ac/third_party/WebKit/Source/core/css/StyleEngineTest.cpp
[modify] https://crrev.com/fcb44ac06933a5f1300db5c0677ffe2a07a569ac/third_party/WebKit/Source/core/css/parser/CSSPropertyParserHelpers.cpp
[modify] https://crrev.com/fcb44ac06933a5f1300db5c0677ffe2a07a569ac/third_party/WebKit/Source/core/css/parser/CSSPropertyParserTest.cpp

ClusterFuzz has detected this issue as fixed in range 523370:523382.

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

Fuzzer: libFuzzer_stylesheet_contents_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: Global-buffer-overflow READ 4
Crash Address: 0x7fd81073c148
Crash State:
  blink::CSSParserToken::GetType
  blink::CSSPropertyParserHelpers::ParseRGBParameters
  blink::CSSPropertyParserHelpers::ParseColorFunction
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=521690:521709
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan_debug&range=523370:523382

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

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.

ClusterFuzz testcase 5244215851483136 is verified as fixed, so closing issue as verified.

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

This bug requires manual review: M64 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), kbleicher@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Regression and fix range are both in 65.

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