This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

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

ClusterFuzz builds the ChromeOS build of ffmpeg so it can fuzz all codecs, but we only ship AMR on ChromeOS.

=>tguilbert who's working on the next ffmpeg roll.

tguilbert: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

ClusterFuzz has detected this issue as fixed in range 452708:452742.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6718529400471552

Fuzzer: libfuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  amr_read_header
  avformat_open_input
  media::FFmpegGlue::OpenContext
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=421508:421597
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=452708:452742

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv942en0m2UD2LJvGpFRS5lJOCrk7a1YxkW1S9KDhVGzjH6lcmixu6FM6f7K0KdWTOa6tIVtudI0V-7ZYytqJMqQzjG366GshvueHCaURH7zeMd0oXb8P9XKhEHZsXWsEUkKFyXf42vLPuvPLy_7fQMB3jUpfD1z_Q2mSsSBFJnud0vYrVpcFCWJsRfopkPEKJjf_HkhDH6cRHgmTqx59AUqWQliSaFBU0padmyUHVunVzaBoMYQhvJnX2dAIGVuCojU3uoYoVK7qokagElISK7ZxD5Rrpp3HJWoMSoVdF3YJJDtFzj9sM6rS2YfJaWgSzHax9OaIpdLVFlQiQ0e3E5SGAG-SjLjSoi2K_wzF3b3twzmaldtItfh1kfSL3Ag3xocX4lSHv_M6qNeGTCqBsyMCJiiKzw?testcase_id=6718529400471552


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 6718529400471552 is verified as fixed, so closing issue.

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