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

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

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

Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/4491ba9d10af731964683f577822e7f29c339bf3 (Add fuzzing target for CSSParserFastPaths.cpp.).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.

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

commit 5def70bc87542c1cc4922a48cfdae9894a79796a
Author: Darren Shen <shend@chromium.org>
Date: Thu Oct 12 23:44:26 2017

Fix preconditions for css_parser_fast_paths_fuzzer.

There's a bug in generating the CSSPropertyID value from the hash of
the data string. We currently do (hash % numCSSPropertyIDs), which
can generate unresolved properties, which are not allowed in the
fuzz target. This patch tries to only generate valid (resolved)
CSSPropertyIDs.

Bug:  774113 ,  774060 ,  774020 ,  774015 
Change-Id: Iaa5655f7399cd0d1381197e7b4026d426b3cf456
Reviewed-on: https://chromium-review.googlesource.com/717276
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#508543}
[modify] https://crrev.com/5def70bc87542c1cc4922a48cfdae9894a79796a/third_party/WebKit/Source/core/css/parser/CSSParserFastPathsFuzzer.cpp

ClusterFuzz has detected this issue as fixed in range 508542:508576.

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

Fuzzer: libFuzzer_css_parser_fast_paths_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Global-buffer-overflow READ 8
Crash Address: 0x0000151fda88
Crash State:
  blink::GetAPI
  blink::CSSPropertyAPI::Get
  blink::ParseKeywordValue
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=508229:508247
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=508542:508576

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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 4977251262398464 is verified as fixed, so closing issue as verified.

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

Both regressed and fixed in M63, removing ReleaseBlock-Stable

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