New issue
Advanced search Search tips

Issue 850389 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in mov_read_saio

Project Member Reported by ClusterFuzz, Jun 7 2018

Issue description

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  mov_read_saio
  mov_read_default
  mov_read_default
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=560371:560389

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Jun 7 2018

Components: Internals>Media>FFmpeg
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

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

Comment 2 by ClusterFuzz, Jun 7 2018

Cc: xhw...@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

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

Comment 3 by ClusterFuzz, Jun 7 2018

Cc: modma...@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

avformat/mov: Increase support for common encryption. by modmaker@google.com - https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/f7221d8e670ec05471a16cc4cc1cc8e0040b5b5f

avformat/mov: Fix parsing of saio/siaz atoms in encrypted content. by modmaker@google.com - https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/e5ba5fab493bd2edb24da47940626b024ebd0371

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
Owner: modma...@google.com
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by ClusterFuzz, Jun 17 2018

Labels: OS-Mac
Project Member

Comment 6 by bugdroid1@chromium.org, Jun 20 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/4e04c9a97b5ec3ec2f038650bcdbe7d902945bd4

commit 4e04c9a97b5ec3ec2f038650bcdbe7d902945bd4
Author: Jacob Trimble <modmaker@google.com>
Date: Wed Jun 20 17:18:17 2018

Fix reading saio/saiz for clear content.

Bug:  850389 
Change-Id: I3faf93bb2a71937b1630d9278935b088cf2c47e8
Reviewed-on: https://chromium-review.googlesource.com/1091214
Reviewed-by: Frank Liberato <liberato@chromium.org>

[modify] https://crrev.com/4e04c9a97b5ec3ec2f038650bcdbe7d902945bd4/libavformat/mov.c
[modify] https://crrev.com/4e04c9a97b5ec3ec2f038650bcdbe7d902945bd4/chromium/patches/README

Project Member

Comment 7 by ClusterFuzz, Jun 21 2018

ClusterFuzz has detected this issue as fixed in range 569095:569115.

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

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  mov_read_saio
  mov_read_default
  mov_read_default
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=560371:560389
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=569095:569115

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

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

Comment 8 by ClusterFuzz, Jun 21 2018

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

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

Sign in to add a comment