New issue
Advanced search Search tips

Issue 659615 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Feb 2017
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in Move_Zp2_Point

Project Member Reported by ClusterFuzz, Oct 26 2016

Issue description

Project Member

Comment 1 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 2 by ClusterFuzz, Feb 28 2017

ClusterFuzz has detected this issue as fixed in range 453210:453213.

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

Fuzzer: ochang_search_index_mutator
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  Move_Zp2_Point
  Ins_SHP
  TT_RunIns
  
Sanitizer: undefined (UBSAN)

Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=409458:409520
Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_ubsan_chrome&range=453210:453213

Reproducer Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94l35yL_456gMzk4MXQTZ75YTPFYGD_NQJbeImaeqU9Rjn_Oy94NzXbvPnmWysiNz5xMonIrtbR-pToJT5HR0amfDqMjrNMKPsu5EA7JoYnKmREd1zlv9flx52nlx1qJ1B9r53GpIMwtoAg_GFTnOkxIS--1sjAFvqQ5JerEZcD9B6cmeg?testcase_id=4829565668294656


See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs 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 3 by ClusterFuzz, Feb 28 2017

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

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

Sign in to add a comment