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

Issue 686619 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Integer-overflow in SkCanvas::onGetLocalClipBounds

Project Member Reported by ClusterFuzz, Jan 30 2017

Issue description

Cc: msrchandra@chromium.org
Components: Internals>Skia
Labels: -Type-Bug Type-Bug-Regression
Owner: reed@chromium.org
Status: Assigned (was: Untriaged)
Predator result:
--------------------
The result is a list of CLs that change the crashed files. 

Author: Mike Reed
Project: chromium-skia
Changelist: https://skia.googlesource.com/skia.git/+/918e144408ba218df919528f8b48c544f4767883
Time: Mon Jan 23 11:39:45 2017 -0500
Lines 31 of file SkBigPicture.cpp which potentially caused crash are changed in this cl (frame #2, "SkBigPicture::playback"). 

Lines 1777-1781 of file SkCanvas.cpp which potentially caused crash are changed in this cl (frame #0, "SkCanvas::onGetLocalClipBounds").
Minimum distance from crash line to modified line: 0. (file: SkBigPicture.cpp, crashed on: 31, modified: 31).

based on predator results assigning to reed@, could you please check the issue and help.
Project Member

Comment 2 by ClusterFuzz, Apr 15 2017

ClusterFuzz has detected this issue as fixed in range 464807:464815.

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

Fuzzer: miaubiz_svg_fuzzer
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  SkCanvas::onGetLocalClipBounds
  getLocalClipBounds
  SkBigPicture::playback
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=445391:445491
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=464807:464815

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv96Fr5oYjPBIWFrjDkz7Q16Z07kbU9rWfo5fsUDgeIHvMOGiBispd07WDNxNCxxPxbM6rs8Q-ZIrrp-f-bPJtgS3eqyO7569JcgiVR-psAwjtXmSvpUuUOqOTkh7dawsZYpQZR9RrxcWCGGPJsUowVyXajQ_hdqr7B49jMhboPhlEl3yHW6WsxouVyfM_PHlwBeDglDHw2wN7YaD23SrOXO3M_a_tLvaNV25n3CCNBbfdYp7HmrxhtshNZHAvl9X-_TjYLUZriipPeDqPJwTYZq29UmXgQ1kZSPlQ3NU_eB9W-d6sIKmzySKumaJzTy1xVeJFTXjz-ejG0UNrJcGc7w5tGxn_9xk0Ohg-pidQ_AhzGZUG4U?testcase_id=5858162055053312


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, Apr 15 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5858162055053312 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