New issue
Advanced search Search tips

Issue 718977 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in v8::internal::ScavengingVisitor<1,1>::EvacuateObject<1,0>

Project Member Reported by ClusterFuzz, May 5 2017

Issue description

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x18680000
Crash State:
  v8::internal::ScavengingVisitor<1,1>::EvacuateObject<1,0>
  v8::internal::ScavengingVisitor<1,1>::EvacuateFixedArray
  v8::internal::Scavenger::ScavengeObjectSlow
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=469085:469168

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Owner: mlippautz@chromium.org
Status: Assigned (was: Untriaged)
mlippautz, PTAL. ClusterFuzz thinks this is caused by:

Author: mlippautz
Project: chromium-v8
Changelist: https://chromium.googlesource.com/v8/v8.git/+/17a0a575a3795141dfccabc688b3fa39f226e186
Time: Wed May 03 13:58:22 2017
Files heap.cc, scavenger.cc are changed in this cl (and is part of stack frame #4, "v8::internal::Heap::Scavenge"; frame #5, "v8::internal::Heap::PerformGarbageCollection"; frame #6, "v8::internal::Heap::CollectGarbage")
Minimum distance from crash line to modified line: 9. (file: heap.cc, crashed on: 1673, modified: 1682).
Project Member

Comment 2 by ClusterFuzz, May 6 2017

ClusterFuzz has detected this issue as fixed in range 469626:469633.

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

Fuzzer: mbarbella_js_mutation
Job Type: windows_asan_d8
Platform Id: windows

Crash Type: UNKNOWN READ
Crash Address: 0x18680000
Crash State:
  v8::internal::ScavengingVisitor<1,1>::EvacuateObject<1,0>
  v8::internal::ScavengingVisitor<1,1>::EvacuateFixedArray
  v8::internal::Scavenger::ScavengeObjectSlow
  
Sanitizer: address (ASAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=469085:469168
Fixed: https://clusterfuzz.com/revisions?job=windows_asan_d8&range=469626:469633

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


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 3 by ClusterFuzz, May 6 2017

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

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

Comment 4 by sheriffbot@chromium.org, May 6 2017

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

Comment 5 by sheriffbot@chromium.org, Aug 12 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
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 28

Labels: Pri-1

Sign in to add a comment