New issue
Advanced search Search tips

Issue 784863 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Security



Sign in to add a comment

CHECK failure: nof_elements <= array_length in objects-debug.cc

Project Member Reported by ClusterFuzz, Nov 14 2017

Issue description

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  nof_elements <= array_length in objects-debug.cc
  v8::platform::PrintStackTrace
  v8::internal::JSArray::JSArrayVerify
  
Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Cc: bmeu...@chromium.org
Owner: danno@chromium.org
Status: Assigned (was: Untriaged)
Reproduces locally.

A debug build crashes with
#
# Fatal error in ../../src/objects-inl.h, line 518
# Debug check failed: IsNumber().
#

Bisects to b590679496e829fd2f88ba4494072f0196c979de (Activate CSA implementation of Array.prototype.slice).
Project Member

Comment 2 by sheriffbot@chromium.org, Nov 15 2017

Labels: Pri-1

Comment 3 by mmoroz@chromium.org, Nov 15 2017

Labels: Security_Impact-Head M-64
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 16 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 5 by ClusterFuzz, Nov 16 2017

ClusterFuzz has detected this issue as fixed in range 49409:49410.

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

Fuzzer: ochang_js_fuzzer_win
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: CHECK failure
Crash Address: 
Crash State:
  nof_elements <= array_length in objects-debug.cc
  v8::platform::PrintStackTrace
  v8::internal::JSArray::JSArrayVerify
  
Sanitizer: address (ASAN)

Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=49409:49410

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

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.

Comment 6 by danno@chromium.org, Nov 16 2017

Status: Fixed (was: Assigned)
Project Member

Comment 7 by ClusterFuzz, Nov 16 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Fixed)
ClusterFuzz testcase 5476863660261376 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 8 by sheriffbot@chromium.org, Nov 17 2017

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

Comment 9 by sheriffbot@chromium.org, Feb 22 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
Project Member

Comment 10 by sheriffbot@chromium.org, Mar 27 2018

Labels: -Security_Impact-Head -M-64 M-65 Security_Impact-Stable
Labels: -ReleaseBlock-Stable

Comment 12 by danno@chromium.org, Jun 20 2018

Cc: jarin@chromium.org
Labels: Hotlist-Torque
Cc: tebbi@chromium.org

Sign in to add a comment