New issue
Advanced search Search tips

Issue 923643 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Null-dereference READ in mov_read_sidx

Project Member Reported by ClusterFuzz, Jan 19 (3 days ago)

Issue description

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

Fuzzer: libFuzzer_audio_decoder_fuzzer
Fuzz target binary: audio_decoder_fuzzer
Job Type: windows_libfuzzer_chrome_asan
Platform Id: windows

Crash Type: Null-dereference READ
Crash Address: 0x0000000000a0
Crash State:
  mov_read_sidx
  mov_read_default
  mov_read_header
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=windows_libfuzzer_chrome_asan&range=617276:617282

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for instructions to reproduce this bug locally.
 
Project Member

Comment 1 by ClusterFuzz, Jan 19 (3 days ago)

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, Jan 19 (3 days ago)

Cc: mmoroz@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, Jan 19 (3 days ago)

Labels: Test-Predator-Auto-Owner
Owner: chcunningham@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/8b857829e499caea0ac4fbd284115aa9347e2e42 (lavf/mov: ensure only one tkhd per trak).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 4 by dalecur...@chromium.org, Today (12 hours ago)

Cc: modma...@google.com

Sign in to add a comment