Issue metadata
Sign in to add a comment
|
Bad-cast to content::RenderFrameHostImpl from invalid vptr |
||||||||||||||||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5585112052006912 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_cfi_chrome Platform Id: linux Crash Type: Bad-cast Crash Address: 0xffffea3520ed6752 Crash State: Bad-cast to content::RenderFrameHostImpl from invalid vptr Recommended Security Severity: High Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_cfi_chrome&range=424760:424853 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv973BSUY08fZ-Nz3xLwBaEctOIrWyphl7n9NnXvJqP18dPhDyVceOBq29_CyaVyk9_FhaQuTJcLa32zrMx13lK83WllghuDnPOxoeBhh-MGYTWMw9ZK0lqDWVVMvz92ied3-do2YWEyrl0ie_rVSycuJJCFhNvReVywHC4m66GiM_8VjNyk?testcase_id=5585112052006912 Issue filed automatically. See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Oct 19 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
,
Oct 19 2016
,
Oct 19 2016
,
Oct 20 2016
ClusterFuzz is analyzing your testcase. Developers can follow the progress at https://cluster-fuzz.appspot.com/testcase?key=5415853229342720
,
Oct 20 2016
ClusterFuzz has detected this issue as fixed in range 426137:426164. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5585112052006912 Fuzzer: ifratric-browserfuzzer-v3 Job Type: linux_cfi_chrome Platform Id: linux Crash Type: Bad-cast Crash Address: 0xffffea3520ed6752 Crash State: Bad-cast to content::RenderFrameHostImpl from invalid vptr Recommended Security Severity: High Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_cfi_chrome&range=424760:424853 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_cfi_chrome&range=426137:426164 Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv973BSUY08fZ-Nz3xLwBaEctOIrWyphl7n9NnXvJqP18dPhDyVceOBq29_CyaVyk9_FhaQuTJcLa32zrMx13lK83WllghuDnPOxoeBhh-MGYTWMw9ZK0lqDWVVMvz92ied3-do2YWEyrl0ie_rVSycuJJCFhNvReVywHC4m66GiM_8VjNyk?testcase_id=5585112052006912 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.
,
Oct 20 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Oct 20 2016
,
Oct 28 2016
,
Jan 26 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
, Oct 19 2016