Issue metadata
Sign in to add a comment
|
Bad-cast to webrtc::MetricsObserverInterface from invalid vptr in cricket::BasicPortAllocator::OnIceRegathering |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5631246427488256 Fuzzer: phoglund_webrtc_peerconnection Job Type: linux_ubsan_vptr_chrome Platform Id: linux Crash Type: Bad-cast Crash Address: 0x1d6f4284a450 Crash State: Bad-cast to webrtc::MetricsObserverInterface from invalid vptr cricket::BasicPortAllocator::OnIceRegathering cricket::BasicPortAllocatorSession::OnNetworksChanged Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_vptr_chrome&range=519266:519277 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5631246427488256 Additional requirements: Requires HTTP Issue filed automatically. See https://github.com/google/clusterfuzz-tools for more information.
,
Dec 6 2017
,
Dec 6 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
,
Dec 6 2017
,
Dec 6 2017
Ok. I'll investigate tomorrow.
,
Dec 7 2017
,
Dec 7 2017
I am unable to reproduce this, I've tried with ubsan, debug and asan builds. Running with --use-fake-device-for-media-stream --use-fake-ui-for-media-stream to get around unrelated permission crash. It's spamming the following in the console: [1:19:1207/145000.702235:ERROR:sctptransport.cc(813)] SctpTransport->SendQueuedStreamResets(): Failed to send a stream reset for 1 streams: [0x00000072] Operation already in progress I'm closing as WontFix (cannot repro) unless someone else wants to give a try. The stack trace looks completely unrelated to the CL linked in #1.
,
Mar 15 2018
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 elawrence@chromium.org
, Dec 5 2017Components: Blink>WebRTC>PeerConnection