Issue metadata
Sign in to add a comment
|
Bad-cast to content::ResourceMessageFilter from invalid vptr;content::ResourceMessageFilter::CreateLoaderAndStart;content::mojom::URLLoaderFactoryStubDispatch::Accept |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4881658682802176 Fuzzer: inferno_layout_test_unmodified Job Type: linux_ubsan_vptr_content_shell_drt Platform Id: linux Crash Type: Bad-cast Crash Address: 0x087dcc69ca20 Crash State: Bad-cast to content::ResourceMessageFilter from invalid vptr content::ResourceMessageFilter::CreateLoaderAndStart content::mojom::URLLoaderFactoryStubDispatch::Accept Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=495868:495869 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4881658682802176 Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Aug 21 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
,
Aug 21 2017
,
Aug 21 2017
May be related to issue 757412 .
,
Aug 21 2017
Re c#4, I suppose you meant either bug 756523 . Adding some folks who have touched loading code most recently. I don't have any ideas yet.
,
Aug 22 2017
Can I get access to issue 756523 and the detailed ClusterFuzz report above?
,
Aug 26 2017
ClusterFuzz has detected this issue as fixed in range 497420:497430. Detailed report: https://clusterfuzz.com/testcase?key=4881658682802176 Fuzzer: inferno_layout_test_unmodified Job Type: linux_ubsan_vptr_content_shell_drt Platform Id: linux Crash Type: Bad-cast Crash Address: 0x087dcc69ca20 Crash State: Bad-cast to content::ResourceMessageFilter from invalid vptr content::ResourceMessageFilter::CreateLoaderAndStart content::mojom::URLLoaderFactoryStubDispatch::Accept Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=495868:495869 Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_content_shell_drt&range=497420:497430 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4881658682802176 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 26 2017
ClusterFuzz testcase 4881658682802176 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Aug 26 2017
,
Oct 5 2017
,
Dec 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
, Aug 21 2017