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

Issue 735218 link

Starred by 1 user
Status: Verified
Owner:
jrumm...@chromium.org
Closed: Nov 2017
Cc:
█ msrchandra@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in mov_read_stts

Project Member Reported by ClusterFuzz, Jun 20 2017 
Detailed report: https://clusterfuzz.com/testcase?key=4855476780269568

Fuzzer: libFuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  mov_read_stts
  mov_read_default
  mov_read_default
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=413192:413325

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


Issue filed automatically.

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

Comment 1 by msrchandra@chromium.org, Sep 19 2017

Cc: msrchandra@chromium.org
Labels: Test-Predator-Wrong M-63
Owner: jrumm...@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL could not provide any possible suspects.
Using Code Search for the file, "mov.c" assigning to the concern owner.

Suspecting Commit#
https://chromium.googlesource.com/chromium/third_party/ffmpeg.git/+/c6832596afabe7208f4fc8b4232be8e65ebb85b0

@jrummell -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by msrchandra@chromium.org, Sep 19 2017 

 Issue 732065  has been merged into this issue.

Comment 3 by mmoroz@chromium.org, Oct 24 2017 

For more information, please see https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md.

The link referenced in the description is no longer valid.

(bulk edit)
Project Member

Comment 4 by ClusterFuzz, Nov 19 2017

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

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

Comment 5 by ClusterFuzz, Nov 26 2017

Labels: Needs-Feedback
ClusterFuzz testcase 4855476780269568 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.
►

Sign in to add a comment