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

Issue 705280 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Email to this user bounced
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in sse2::blit_row_s32a_opaque

Project Member Reported by ClusterFuzz, Mar 26 2017

Issue description

Project Member

Comment 1 by sheriffbot@chromium.org, Mar 26 2017

Labels: M-59
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 26 2017

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

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

Comment 3 by sheriffbot@chromium.org, Mar 26 2017

Labels: Pri-1
Components: Internals>Skia
Owner: reed@chromium.org
Status: Assigned (was: Untriaged)
reed@, could you take a look to see if this is related to your recent change https://skia.googlesource.com/skia.git/+/2f6b5a47a50cdd218bc3302273be3a4a71add8fb?

Thanks!
Project Member

Comment 5 by ClusterFuzz, Mar 29 2017

ClusterFuzz has detected this issue as fixed in range 460139:460163.

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

Fuzzer: tokenfuzz_pdf_curated
Job Type: linux_msan_pdfium
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  sse2::blit_row_s32a_opaque
  walk_convex_edges
  SkScan::FillTriangle
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_pdfium&range=458746:458879
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_pdfium&range=460139:460163

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv95K_sVI1KLPbId76S7p570U1TyxiSufKsjZT9oDjZYl2IdJWcG_YYLfK8pr2r3FK7t84Xs9AeE7FL6lYB4gX5h0tbFFFu4RHfFVDKLQ9ZOP1HM-1BH6RtECcMWkPuefdr7vg8M0MDn3Xi-vEuXNLwh41Iy7J-6EAncJF8taFYLXvqzgYs-BVG6YCJ4rZjbWPzClUFlrQ-H_2cE69zHjQK3UcKEaqVhtjyq3SodiEGFCJb_R0Cb-Ryggf1xhgQT_3TeW9c6RTfBwE75bs4HYiFxPv38mGsiwSaAtn6rDPDh9dEvVmE4zpBk1ogxtSyoG407-dtCRQ6wXZikyU4v2lepmGmhnB2LeL12bolDqp9P6ZUomUslc8YlOxmey3GlJnlZ-l4ToHaprJCf1GWASxCWN8OCR0Q?testcase_id=6267766215802880


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 6 by ClusterFuzz, Mar 29 2017

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

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

Comment 7 by sheriffbot@chromium.org, Mar 29 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Beta
Project Member

Comment 9 by sheriffbot@chromium.org, Jul 5 2017

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