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

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

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

+awhalley@ could you ptal and assign to appropriate dev pls?

This'll get picked up by the chrome security sheriff for triage. Setting labels as we don't need to block M65 on this.

ClusterFuzz has detected this issue as fixed in range 539126:539132.

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

Fuzzer: libFuzzer_swiftshader_vertex_routine_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x60300000983c
Crash State:
  TIntermConstantUnion::fold
  TParseContext::addFunctionCallOrMethod
  yyparse
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=521502:521564
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=539126:539132

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

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 4735389718544384 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 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