Issue metadata
Sign in to add a comment
|
Use-after-poison in blink::CrossThreadPersistentRegion::prepareForThreadStateTermination |
||||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6166696889155584 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_chrome Platform Id: mac Crash Type: Use-after-poison READ 8 Crash Address: 0x7eb14bc0c830 Crash State: blink::CrossThreadPersistentRegion::prepareForThreadStateTermination blink::ThreadState::runTerminationGC blink::ThreadHeap::detach Recommended Security Severity: High Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=398867:398897 Minimized Testcase (2.39 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94I8ZHEi-iQfXaoPWRA9tUYmrgIQyuzeSf75RA4DF9IMnY_ATc0uYU1QSa-Cn_BpWvvw076K9iDEZ4-z-zQpncAJ2JluYfB3Sa5XQNhxoWWYapM2cW7r_ui7mdBrA5wPkoeu3AuQfUTnECNzxqJ16TWoK1mcQ Additional requirements: Requires HTTP Filer: inferno See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jun 12 2016
Due to the CrossThreadPersistent<> usage introduced in https://codereview.chromium.org/2025783002
,
Jun 12 2016
Having CrossThreadPersistent<> as members of heap objects means you have to take care of the effects of lazy sweeping. i.e., annotating the WebSocket object which uses that persistent with EAGERLY_FINALIZE() (next to its DECLARE_TRACE()), will most likely take care of it.
,
Jun 12 2016
,
Jun 12 2016
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 12 2016
,
Jun 13 2016
,
Jun 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5c41255da77e26cfd08bc1ff29f09214dba3bea4 commit 5c41255da77e26cfd08bc1ff29f09214dba3bea4 Author: sigbjornf <sigbjornf@opera.com> Date: Mon Jun 13 13:34:34 2016 Promptly release cross-thread websocket bridge/proxy references To prevent other threads using cross-thread persistents from accessing to-be-finalized websocket Peer and Bridge abstractions, promptly free them on becoming garbage. Delaying this until lazy sweeping runs risks (benignly) touching poisoned objects. R= BUG= 619373 Review-Url: https://codereview.chromium.org/2064633002 Cr-Commit-Position: refs/heads/master@{#399442} [modify] https://crrev.com/5c41255da77e26cfd08bc1ff29f09214dba3bea4/third_party/WebKit/Source/modules/websockets/WorkerWebSocketChannel.h
,
Jun 13 2016
,
Jun 13 2016
,
Jun 14 2016
ClusterFuzz has detected this issue as fixed in range 399438:399445. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6166696889155584 Fuzzer: inferno_layout_test_unmodified Job Type: mac_asan_chrome Platform Id: mac Crash Type: Use-after-poison READ 8 Crash Address: 0x7eb14bc0c830 Crash State: blink::CrossThreadPersistentRegion::prepareForThreadStateTermination blink::ThreadState::runTerminationGC blink::ThreadHeap::detach Recommended Security Severity: High Regressed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=398867:398897 Fixed: https://cluster-fuzz.appspot.com/revisions?job=mac_asan_chrome&range=399438:399445 Minimized Testcase (2.39 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94I8ZHEi-iQfXaoPWRA9tUYmrgIQyuzeSf75RA4DF9IMnY_ATc0uYU1QSa-Cn_BpWvvw076K9iDEZ4-z-zQpncAJ2JluYfB3Sa5XQNhxoWWYapM2cW7r_ui7mdBrA5wPkoeu3AuQfUTnECNzxqJ16TWoK1mcQ Additional requirements: Requires HTTP 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.
,
Jun 14 2016
,
Jun 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5c41255da77e26cfd08bc1ff29f09214dba3bea4 commit 5c41255da77e26cfd08bc1ff29f09214dba3bea4 Author: sigbjornf <sigbjornf@opera.com> Date: Mon Jun 13 13:34:34 2016 Promptly release cross-thread websocket bridge/proxy references To prevent other threads using cross-thread persistents from accessing to-be-finalized websocket Peer and Bridge abstractions, promptly free them on becoming garbage. Delaying this until lazy sweeping runs risks (benignly) touching poisoned objects. R= BUG= 619373 Review-Url: https://codereview.chromium.org/2064633002 Cr-Commit-Position: refs/heads/master@{#399442} [modify] https://crrev.com/5c41255da77e26cfd08bc1ff29f09214dba3bea4/third_party/WebKit/Source/modules/websockets/WorkerWebSocketChannel.h
,
Jun 16 2016
Issue 620754 has been merged into this issue.
,
Jul 26 2016
Fix already in M53, removing ReleaseBlock-Beta.
,
Sep 20 2016
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
,
Oct 1 2016
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
,
Oct 2 2016
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
,
Oct 2 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by infe...@chromium.org
, Jun 12 2016Owner: sigbjo...@opera.com
Status: Assigned (was: Available)