Author: danilchap
Project: chromium-webrtc
Changelist: https://chromium.googlesource.com/external/webrtc/trunk/webrtc.git/+/8262976b30119307af82f875c3ad7821c5d94d7f
Time: Wed Nov 09 13:46:39 2016
The CL last changed line 82 of file rtp_header_extension.h, which is stack frame 4.

valid DCHECK fired: invalid parameter of 0 passed as an argument. revealed with mentioned CL https://codereview.webrtc.org/2452293004/ .

In release it wouldn't cause a crash and worst case would treat a valid packet as invalid. Same way before and after changes added with the DCHECK. (our version of webrtc/rtp doesn't produce that kind of packets).

Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/external/webrtc.git/+/b7374dba6b45824f45d7fa324ebfb0d52fb4b4f0

commit b7374dba6b45824f45d7fa324ebfb0d52fb4b4f0
Author: danilchap <danilchap@webrtc.org>
Date: Thu Nov 24 17:06:05 2016

Fix parsing padding byte in rtp header extension

BUG= chromium:664598 

Review-Url: https://codereview.webrtc.org/2498903003
Cr-Commit-Position: refs/heads/master@{#15230}

[modify] https://crrev.com/b7374dba6b45824f45d7fa324ebfb0d52fb4b4f0/webrtc/modules/BUILD.gn
[modify] https://crrev.com/b7374dba6b45824f45d7fa324ebfb0d52fb4b4f0/webrtc/modules/rtp_rtcp/source/rtp_utility.cc
[modify] https://crrev.com/b7374dba6b45824f45d7fa324ebfb0d52fb4b4f0/webrtc/modules/rtp_rtcp/source/rtp_utility.h
[add] https://crrev.com/b7374dba6b45824f45d7fa324ebfb0d52fb4b4f0/webrtc/modules/rtp_rtcp/source/rtp_utility_unittest.cc

ClusterFuzz has detected this issue as fixed in range 434441:434469.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5232538542145536

Fuzzer: libfuzzer_rtp_header_fuzzer
Job Type: libfuzzer_chrome_asan_debug
Platform Id: linux

Crash Type: UNKNOWN
Crash Address: 0x03e900006768
Crash State:
  rtc::FatalMessage::~FatalMessage
  webrtc::RtpHeaderExtensionMap::GetType
  webrtc::RtpHeaderExtensionMap::GetType
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=431367:431432
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_asan_debug&range=434441:434469

Minimized Testcase (0.03 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94D5dwz--PKszpfITOByvz9QDwDwSKXBZVhtUXHFYxrpIac-o2ySsmYQy-sSArPoQux9C7lF5RBvUbiYphMNxzXtLgPtUINrA74lW89xP12Y6vxHdOZcxOyKtJdpJ2P3-0LpAJRCc5JxNLBbF9LIotzPYH6cQ?testcase_id=5232538542145536

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase is verified as fixed, closing issue.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.