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 adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

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

commit cd02a4924f70f933e2be62d962c9505558dbeeac
Author: Xiaohan Wang <xhwang@chromium.org>
Date: Thu Jan 17 00:53:28 2019

media: Check |size| in WebMContentEncodingsClient::OnBinary()

The parser allows zero data size for Binary data. However, we should not
allow empty ContentEncKeyID.

Bug:  922155 
Change-Id: I768ecccd7e885736d4d24940f5cc65c1c607818c
Reviewed-on: https://chromium-review.googlesource.com/c/1413787
Commit-Queue: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Kongqun Yang <kqyang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#623478}
[modify] https://crrev.com/cd02a4924f70f933e2be62d962c9505558dbeeac/media/formats/webm/webm_content_encodings_client.cc

ClusterFuzz has detected this issue as fixed in range 623461:623494.

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

Fuzzer: libFuzzer_mediasource_WEBM_OPUS_pipeline_integration_fuzzer
Fuzz target binary: mediasource_WEBM_OPUS_pipeline_integration_fuzzer
Job Type: x86_libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: CHECK failure
Crash Address: 
Crash State:
  size > 0 in webm_content_encodings_client.cc
  media::WebMContentEncodingsClient::OnBinary
  media::ParseBinary
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=x86_libfuzzer_chrome_asan_debug&range=623461:623494

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

See https://github.com/google/clusterfuzz-tools for instructions to reproduce this bug locally.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

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

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