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

Issue 707785 link

Starred by 2 users

Issue metadata

Status: Verified
Owner: ----
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Integer-overflow in XRect_roundOut

Project Member Reported by ClusterFuzz, Apr 3 2017

Issue description

Components: Internals>Skia
Labels: Test-Predator-Wrong M-59
Owner: jbroman@chromium.org
Status: Assigned (was: Untriaged)
Through code search on file SkScan_Antihair.cpp, suspected CL is 
https://skia.googlesource.com/skia.git/+/20fbada09bbcc31d128959a8e4d4cac499741505
jbroman@, could you please take a look?
Thank you.

Comment 3 Deleted

Owner: caryclark@chromium.org
I don't see how that CL could be the cause. Assigning to caryclark@ (current Skia sheriff AFAICT) for triage.
Cc: hcm@chromium.org caryclark@google.com aarya@google.com reed@google.com
Owner: ----
Status: Available (was: Assigned)
There's no process at the moment to isolate this within Skia.
Taking myself off as the owner as I am not able to help out at this time.

Comment 6 by hcm@chromium.org, Apr 7 2017

Labels: -Pri-2 Pri-3
Lowering severity on non-security int overflows as we need to prioritize other issues at this time.
Project Member

Comment 7 by ClusterFuzz, May 25 2017

ClusterFuzz has detected this issue as fixed in range 474169:474185.

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  XRect_roundOut
  SkScan::AntiFillXRect
  aa_square_proc
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=456626:457730
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=474169:474185

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


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 8 by ClusterFuzz, May 25 2017

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