Issue metadata
Sign in to add a comment
|
Crash in v8::internal::Invoke |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5493096547876864 Fuzzer: inferno_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000100000008 Crash State: v8::internal::Invoke v8::internal::CallInternal v8::internal::Object::GetPropertyWithDefinedGetter Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48005:48006 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5493096547876864 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Sep 15 2017
,
Sep 15 2017
,
Sep 15 2017
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
,
Sep 15 2017
,
Sep 15 2017
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/8557eb03f9753a37bb8f9f6a547b332538fc22a4 commit 8557eb03f9753a37bb8f9f6a547b332538fc22a4 Author: Albert Mingkun Yang <albertnetymk@google.com> Date: Fri Sep 15 15:01:56 2017 Deserialize RecordWrite stub eagerly Since DeserializeLazy uses write barrier, deserializing write barrier lazily would cause cyclic dependency. This commit changes RecordWrite to be deserializd eagerly. Bug: chromium:765301 chromium:749486 Change-Id: I363692baf9b742289c0443afac634662f0026922 Reviewed-on: https://chromium-review.googlesource.com/668454 Commit-Queue: Albert Mingkun Yang <albertnetymk@google.com> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#48044} [modify] https://crrev.com/8557eb03f9753a37bb8f9f6a547b332538fc22a4/src/builtins/builtins.cc
,
Sep 23 2017
ClusterFuzz has detected this issue as fixed in range 48122:48123. Detailed report: https://clusterfuzz.com/testcase?key=5493096547876864 Fuzzer: inferno_js_fuzzer Job Type: linux_asan_d8_dbg Platform Id: linux Crash Type: UNKNOWN READ Crash Address: 0x000100000008 Crash State: v8::internal::Invoke v8::internal::CallInternal v8::internal::Object::GetPropertyWithDefinedGetter Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48005:48006 Fixed: https://clusterfuzz.com/revisions?job=linux_asan_d8_dbg&range=48122:48123 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5493096547876864 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 23 2017
ClusterFuzz testcase 5493096547876864 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Sep 23 2017
,
Sep 29 2017
Issue 767816 has been merged into this issue.
,
Nov 3 2017
,
Dec 30 2017
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
,
Mar 27 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by clemensh@chromium.org
, Sep 15 2017Owner: u...@chromium.org
Status: Assigned (was: Untriaged)