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

Issue 863245 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Oct 18
Cc:
Components:
EstimatedDays: ----
NextAction: 2019-01-31
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in compute_pkt_fields

Project Member Reported by ClusterFuzz, Jul 12

Issue description

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

Fuzzer: libFuzzer_audio_decoder_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  compute_pkt_fields
  parse_packet
  read_frame_internal
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=546308:546319

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jul 12

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, Jul 12

Labels: Test-Predator-Auto-Owner
Owner: mmoroz@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/4b5068a99a84ff2edb34aa0549afc89aa751ccb4 (Add audio_decoder_fuzzer fuzz target.).

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.
Cc: wolenetz@chromium.org
Owner: liber...@chromium.org
Cc: liber...@chromium.org
Owner: tguilbert@chromium.org
=>tguilbert as next ffmpeg roll owner.
Cc: -liber...@chromium.org hubbe@chromium.org
Status: Started (was: Assigned)
NextAction: 2018-11-19
Status: Fixed (was: Started)
Fixed upstream. Should be picked up by the next roll.

https://github.com/FFmpeg/FFmpeg/commit/079d1a7175c4b881631a7e7f449c4c13b761cdeb#diff-b45fad75a4dfb82ef50e978d38dc2649

I'm adding a ping in the future to make sure this was indeed fixed after the next roll.
Project Member

Comment 8 by ClusterFuzz, Oct 25

Labels: Needs-Feedback
ClusterFuzz testcase 4775945102426112 is still reproducing on tip-of-tree build (trunk).

Please re-test your fix against this testcase and if the fix was incorrect or incomplete, please re-open the bug. Otherwise, ignore this notification and add ClusterFuzz-Wrong label.
The NextAction date has arrived: 2018-11-19
NextAction: 2018-12-03
Roll not started. Will check back when it is done.
The NextAction date has arrived: 2018-12-03
NextAction: 2018-12-12
Roll still not started.
The NextAction date has arrived: 2018-12-12
NextAction: 2019-01-03
Roll not finished.
The NextAction date has arrived: 2019-01-03
NextAction: 2019-01-31
Still no roll.

Sign in to add a comment