Global-buffer-overflow in blink::BindingSecurity::shouldAllowAccessTo |
|||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5567815957610496 Fuzzer: lcamtuf_cross_fuzz Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: Global-buffer-overflow READ 8 Crash Address: 0x7f40bbf7a218 Crash State: blink::BindingSecurity::shouldAllowAccessTo blink::EventTargetV8Internal::dispatchEventMethodCallback v8::internal::FunctionCallbackArguments::Call Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=445305:445309 Minimized Testcase (5.42 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97SIkjIz9Qxj-w6e0tBCvOBT78fznt1xlgZZEs9AAigg8-_qVoiQpebclTLsX3x9AGibKNIS0JANAmaSRYSkoMGct7DbAiSmLIHz4lnBTr26P15skfBeZSuxuHHf5Rj6mPSCVyzSiw6XonnIyNEeISu-ZpGXR542tx3IqoEHEqhG4C6V_qrlbKMfEVbknimZoIi8Z-6kh7CSn7TNowAQyyVSqV-xNsrZ7kq43vZ6nC97I0dKhQo7I-SgBajAGDsGbWvmDbEOoBKfNRkvn3fKO8m8o30WMEb9bsnOqWO9QIt_tz6PvUnfYFoybIn04T2E7iDY1LXLHv1muc7Ro7i1dukPDkAYA7sSXabwWU3uk3accrjfDg?testcase_id=5567815957610496 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jan 23 2017
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
,
Jan 23 2017
,
Jan 24 2017
I'm assuming this affects all our Blink platforms. Any chance you can triage this one, yukishiino?
,
Jan 24 2017
,
Jan 24 2017
ClusterFuzz has detected this issue as fixed in range 445350:445373. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5567815957610496 Fuzzer: lcamtuf_cross_fuzz Job Type: linux_asan_chrome_chromeos Platform Id: linux Crash Type: Global-buffer-overflow READ 8 Crash Address: 0x7f40bbf7a218 Crash State: blink::BindingSecurity::shouldAllowAccessTo blink::EventTargetV8Internal::dispatchEventMethodCallback v8::internal::FunctionCallbackArguments::Call Sanitizer: address (ASAN) Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=445305:445309 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_asan_chrome_chromeos&range=445350:445373 Minimized Testcase (5.42 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97SIkjIz9Qxj-w6e0tBCvOBT78fznt1xlgZZEs9AAigg8-_qVoiQpebclTLsX3x9AGibKNIS0JANAmaSRYSkoMGct7DbAiSmLIHz4lnBTr26P15skfBeZSuxuHHf5Rj6mPSCVyzSiw6XonnIyNEeISu-ZpGXR542tx3IqoEHEqhG4C6V_qrlbKMfEVbknimZoIi8Z-6kh7CSn7TNowAQyyVSqV-xNsrZ7kq43vZ6nC97I0dKhQo7I-SgBajAGDsGbWvmDbEOoBKfNRkvn3fKO8m8o30WMEb9bsnOqWO9QIt_tz6PvUnfYFoybIn04T2E7iDY1LXLHv1muc7Ro7i1dukPDkAYA7sSXabwWU3uk3accrjfDg?testcase_id=5567815957610496 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.
,
Jan 24 2017
ClusterFuzz testcase 5567815957610496 is verified as fixed, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jan 24 2017
,
Jan 27 2017
Regression and fix ranges both in 58
,
May 2 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 |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by sheriffbot@chromium.org
, Jan 23 2017