New issue
Advanced search Search tips

Issue 772666 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Oct 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 3
Type: Bug-Security



Sign in to add a comment

Heap-use-after-free in SkPathRef::countVerbs

Project Member Reported by ClusterFuzz, Oct 7 2017

Issue description

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x60b000000488
Crash State:
  SkPathRef::countVerbs
  SkPath::isEmpty
  GrCCPRCoverageOpsBuilder::parsePath
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=507290:507291

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Oct 7 2017

Labels: Test-Predator-AutoOwner
Owner: csmartdalton@google.com
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://skia.googlesource.com/skia/+/196efbf71cdd9a64b807e5e869cd45da5a66ac36 (Enable coverage counting path rendering except on Android framework).

If this is incorrect, please remove the owner and apply the Test-Predator-Wrong-CLs label.
Project Member

Comment 2 by sheriffbot@chromium.org, Oct 8 2017

Labels: M-63
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 8 2017

Labels: ReleaseBlock-Stable
This is a serious security regression. If you are not able to fix this quickly, please revert the change that introduced it.

If this doesn't affect a release branch, or has not been properly classified for severity, please update the Security_Impact or Security_Severity labels, and remove the ReleaseBlock label. To disable this altogether, apply ReleaseBlock-NA.

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

Comment 4 by sheriffbot@chromium.org, Oct 8 2017

Labels: Pri-1
Labels: -Pri-1 -Security_Impact-Head Security_Impact-None Pri-3
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 9 2017

Labels: -ReleaseBlock-Stable
Project Member

Comment 7 by ClusterFuzz, Oct 10 2017

Labels: OS-Mac
Project Member

Comment 8 by ClusterFuzz, Oct 11 2017

ClusterFuzz has detected this issue as fixed in range 507658:507671.

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

Fuzzer: libFuzzer_paint_op_buffer_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Heap-use-after-free READ 4
Crash Address: 0x60b000000488
Crash State:
  SkPathRef::countVerbs
  SkPath::isEmpty
  GrCCPRCoverageOpsBuilder::parsePath
  
Sanitizer: address (ASAN)

Recommended Security Severity: High

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=507290:507291
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=507658:507671

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

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md 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 9 by ClusterFuzz, Oct 11 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6613545889562624 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 10 by sheriffbot@chromium.org, Oct 12 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -Test-Predator-AutoOwner Test-Predator-Auto-Owner

Comment 12 by mmoroz@google.com, Nov 27 2017

Cc: enne@chromium.org
Project Member

Comment 13 by sheriffbot@chromium.org, Jan 17 2018

Labels: -Restrict-View-SecurityNotify allpublic
This bug has been closed for more than 14 weeks. Removing security view restrictions.

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

Sign in to add a comment