Issue metadata
Sign in to add a comment
|
CHECK failure: 0 < icu_length in intl-objects.cc |
||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4668882665865216 Fuzzer: ochang_js_fuzzer Job Type: linux_d8_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: 0 < icu_length in intl-objects.cc Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_d8_dbg&range=54689:54690 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4668882665865216 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 10
,
Aug 10
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/7e9ce60d0832176c0a51f6ca612aacd95d53b4f0 commit 7e9ce60d0832176c0a51f6ca612aacd95d53b4f0 Author: Sathya Gunasekaran <gsathya@chromium.org> Date: Fri Aug 10 18:37:41 2018 [Intl] Use JSObject with null proto to prevent side effects Previously, we created a JSObject with a non null prototype for an internal object which isn't what we want as it casues side effects. Bug: chromium:872514 Cq-Include-Trybots: luci.v8.try:v8_linux_noi18n_rel_ng Change-Id: I3318044a03318f3d7099f3ba889450c651cea9e1 Reviewed-on: https://chromium-review.googlesource.com/1171186 Reviewed-by: Adam Klein <adamk@chromium.org> Commit-Queue: Sathya Gunasekaran <gsathya@chromium.org> Cr-Commit-Position: refs/heads/master@{#55062} [modify] https://crrev.com/7e9ce60d0832176c0a51f6ca612aacd95d53b4f0/src/objects/intl-objects.cc [add] https://crrev.com/7e9ce60d0832176c0a51f6ca612aacd95d53b4f0/test/intl/regress-8725514.js
,
Aug 10
,
Aug 11
ClusterFuzz has detected this issue as fixed in range 55061:55062. Detailed report: https://clusterfuzz.com/testcase?key=4668882665865216 Fuzzer: ochang_js_fuzzer Job Type: linux_d8_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: 0 < icu_length in intl-objects.cc Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=linux_d8_dbg&range=54689:54690 Fixed: https://clusterfuzz.com/revisions?job=linux_d8_dbg&range=55061:55062 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4668882665865216 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.
,
Aug 11
ClusterFuzz testcase 4668882665865216 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Aug 11
,
Oct 3
,
Nov 17
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: gsat...@chromium.org
Status: Assigned (was: Untriaged)