Issue metadata
Sign in to add a comment
|
DCHECK failure in !name->AsArrayIndex(&index) in lookup-inl.h |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=6674100354023424 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: !name->AsArrayIndex(&index) in lookup-inl.h v8::internal::LookupIterator::LookupIterator v8::internal::JSObject::AddProperty Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=54991:54992 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6674100354023424 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 9
,
Aug 9
,
Aug 10
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
,
Aug 15
flang: This is a high severity vulnerability, have you had a chance to take a look at your CL? If this can't be fixed quickly the CL should be reverted.
,
Aug 23
ftang: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5
,
Sep 7
ftang: Uh oh! This issue still open and hasn't been updated in the last 29 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers? If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one? If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started. Thanks for your time! To disable nags, add the Disable-Nags label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 7
Hi @ftang, any movement here? It seems like you are the right owner here, and if you are not, can you assign a better one?
,
Sep 12
ClusterFuzz has detected this issue as fixed in range 55784:55785. Detailed report: https://clusterfuzz.com/testcase?key=6674100354023424 Fuzzer: ochang_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: DCHECK failure Crash Address: Crash State: !name->AsArrayIndex(&index) in lookup-inl.h Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=54991:54992 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=55784:55785 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6674100354023424 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.
,
Sep 12
ClusterFuzz testcase 6674100354023424 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 12
,
Sep 14
,
Sep 14
This bug requires manual review: M70 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 14
,
Oct 3
Looks like this was fixed by https://chromiumdash.appspot.com/commit/c62b0634f3103a0e48d418b2637981c715dfe631 - requesting merge to M70
,
Oct 3
This bug requires manual review: We are only 12 days from stable. Please contact the milestone owner if you have questions. Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 4
+abdulsyed@ for merge review
,
Oct 4
How safe is this merge overall and why is it critical? This seems like a huge change.
,
Oct 5
ftang@ - could you speak to the risk of the change?
,
Oct 8
per chat, tracking for M71
,
Nov 8
,
Dec 19
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 |
|||||||||||||||||||||||
Comment 1 by ClusterFuzz
, Aug 9Owner: ftang@chromium.org
Status: Assigned (was: Untriaged)