Issue metadata
Sign in to add a comment
|
Crash in webrtc::ForwardErrorCorrection::XorPayloads |
||||||||||||||||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4526464436011008 Fuzzer: libFuzzer_ulpfec_receiver_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: UNKNOWN WRITE Crash Address: 0x3b268dde9000 Crash State: webrtc::ForwardErrorCorrection::XorPayloads webrtc::ForwardErrorCorrection::RecoverPacket webrtc::ForwardErrorCorrection::AttemptRecovery Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=574542:574544 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4526464436011008 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Jul 16
,
Jul 16
,
Jul 16
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
,
Jul 16
,
Jul 16
Reverted the change where it was introduced. https://webrtc-review.googlesource.com/c/src/+/88720
,
Jul 16
Rolled into chromium in https://chromium-review.googlesource.com/c/chromium/src/+/1138196
,
Jul 16
,
Jul 17
ClusterFuzz has detected this issue as fixed in range 575257:575272. Detailed report: https://clusterfuzz.com/testcase?key=4526464436011008 Fuzzer: libFuzzer_ulpfec_receiver_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: UNKNOWN WRITE Crash Address: 0x3b268dde9000 Crash State: webrtc::ForwardErrorCorrection::XorPayloads webrtc::ForwardErrorCorrection::RecoverPacket webrtc::ForwardErrorCorrection::AttemptRecovery Sanitizer: undefined (UBSAN) Recommended Security Severity: High Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=574542:574544 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=575257:575272 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4526464436011008 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Jul 17
ClusterFuzz testcase 4526464436011008 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Jul 17
,
Aug 15
,
Oct 23
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 ClusterFuzz
, Jul 16Labels: Test-Predator-Auto-CC