New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 683211 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in av_malloc

Project Member Reported by ClusterFuzz, Jan 20 2017

Issue description

Project Member

Comment 1 by sheriffbot@chromium.org, Jan 21 2017

Labels: M-56
Project Member

Comment 2 by sheriffbot@chromium.org, Jan 21 2017

Labels: Pri-1

Comment 3 by palmer@chromium.org, Jan 24 2017

Cc: ddorwin@chromium.org
Components: Internals>Media>FFmpeg
Labels: -OS-Linux OS-All
Owner: dalecur...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to dalecurtis for further triage.
Cc: hubbe@chromium.org dalecur...@chromium.org
Owner: liber...@chromium.org
Status: Started (was: Assigned)
i can repro this locally.  will take a look.
flac parser isn't checking that avio_read is reading the requested 4 byte flac block header (flacdec.c:68).  the uninitialized buffer is then being used to construct the requested av_malloc size.

will send to michael to see if he agrees, then cherry-pick from upstream.
Project Member

Comment 7 by ClusterFuzz, Jan 31 2017

ClusterFuzz has detected this issue as fixed in range 447059:447171.

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

Fuzzer: libfuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  av_malloc
  av_mallocz
  flac_read_header
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=413228:413328
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_msan&range=447059:447171

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv97PNjZoRGfQ4Xi_TQ7lwjdKh1-Ll2qE9x4zwmXBNcXhh3Vctv87WrEwcJ1HIrPn2vvgjo4NfoMULgr8k_OK_Y8mAmjIoyaRN2MaZFEhDEt3mXa_6KVsGyqaqFkQsFB4qDCQ6LOxo6k7jy8jhh3j1KNmqtgHkUDu4tNzRuRn5KAN-Z6sMdDe3oKUY08NMVoT0QMSd4n-lfYhwWLCgFuOifSLA83hprf3RkeCIyWx-A_oMGxidKSObz7YfZqniE-nGplM3yK56wkPGJqnJITk4YxAPiVQNm1sHpc5jZ6WULRqH3ej-Fl8HZPv2AFuUCYZuWzQeNGYZNoEb8LqsL9X97hb731BnrAavQUMM7OW41kg8pXlSi8?testcase_id=5089927294615552


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.
Project Member

Comment 8 by ClusterFuzz, Jan 31 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Started)
ClusterFuzz testcase 5089927294615552 is verified as fixed, so closing issue.

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

Comment 9 by sheriffbot@chromium.org, Jan 31 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -M-56 M-58
Labels: Release-0-M58
Project Member

Comment 12 by sheriffbot@chromium.org, May 9 2017

Labels: -Restrict-View-SecurityNotify allpublic
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

Sign in to add a comment