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

Issue 834534 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 827667
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Security



Sign in to add a comment

Heap-buffer-overflow in angle::LoadToNative<signed

Project Member Reported by ClusterFuzz, Apr 19 2018

Issue description

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

Fuzzer: webDEViL_webgl
Job Type: windows_asan_chrome_with_gpu
Platform Id: windows

Crash Type: Heap-buffer-overflow READ {*}
Crash Address: 0x12f10b731b84
Crash State:
  angle::LoadToNative<signed
  rx::Image11::loadData
  rx::TextureD3D::initializeContents
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 

Comment 1 by aarya@google.com, Apr 19 2018

Cc: zmo@chromium.org
Components: Internals>GPU>Internals
Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)
This is coming from our new shiny gce bots with nvidia gpus.

Comment 2 by aarya@google.com, Apr 19 2018

Cc: kbr@chromium.org
Components: -Internals>GPU>Internals Internals>GPU>ANGLE
Owner: geoffl...@chromium.org

Comment 3 Deleted

Comment 4 Deleted

Status: Assigned (was: Verified)
Not fixed, c#3,#4 were flake.

Comment 6 by aarya@google.com, Apr 19 2018

Cc: geoffl...@chromium.org
Owner: cwallez@chromium.org
Yet another regression from https://chromium.googlesource.com/angle/angle/+/56c8577b4dbf2239780e38090dadbeb06f4b8563
Project Member

Comment 7 by ClusterFuzz, Apr 20 2018

ClusterFuzz has detected this issue as fixed in range 552146:552148.

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

Fuzzer: webDEViL_webgl
Job Type: windows_asan_chrome_with_gpu
Platform Id: windows

Crash Type: Heap-buffer-overflow READ {*}
Crash Address: 0x12f10b731b84
Crash State:
  angle::LoadToNative<signed
  rx::Image11::loadData
  rx::TextureD3D::initializeContents
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=552146:552148

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

See https://github.com/google/clusterfuzz-tools 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 sheriffbot@chromium.org, Apr 20 2018

Labels: M-67
Project Member

Comment 9 by sheriffbot@chromium.org, Apr 20 2018

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 10 by sheriffbot@chromium.org, Apr 20 2018

Labels: Pri-1
Project Member

Comment 11 by sheriffbot@chromium.org, Apr 21 2018

Labels: -Security_Impact-Head Security_Impact-Beta
Mergedinto: 836131
Status: Duplicate (was: Assigned)
Project Member

Comment 13 by ClusterFuzz, Apr 24 2018

ClusterFuzz has detected this issue as fixed in range 552581:552589.

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

Fuzzer: webDEViL_webgl
Job Type: windows_asan_chrome_with_gpu
Platform Id: windows

Crash Type: Heap-buffer-overflow READ {*}
Crash Address: 0x12f10b731b84
Crash State:
  angle::LoadToNative<signed
  rx::Image11::loadData
  rx::TextureD3D::initializeContents
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=550440:550450
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_chrome_with_gpu&range=552581:552589

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

See https://github.com/google/clusterfuzz-tools 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 14 by sheriffbot@chromium.org, Apr 25 2018

Labels: -reward-topanel reward-ineligible
Mergedinto: -836131 827667
Project Member

Comment 16 by sheriffbot@chromium.org, Aug 1

Labels: -Restrict-View-SecurityTeam 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