New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 667028 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Undefined-shift in webrtc::Normal::Process

Project Member Reported by ClusterFuzz, Nov 19 2016

Issue description

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

Fuzzer: libfuzzer_neteq_rtp_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  webrtc::Normal::Process
  webrtc::NetEqImpl::DoNormal
  webrtc::NetEqImpl::GetAudioInternal
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=432467:432520

Minimized Testcase (0.21 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97IOV_wno37tCOPCtXH3psh2VmCMBS8udAIluYn0_Q-UGsjL_ZDmU72Cxo3338fwezK_ON0eZAneeoM6YtehoGmo1q-WlMEKO0rnrH_Q5kRsRbjK-WK8nm0i3AGYgJB7ElJaz4vGwZBIOCz37KpPqjgWlYuUA?testcase_id=4895682210299904

Issue filed automatically.

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

Comment 1 by ajha@chromium.org, Nov 21 2016

Components: Blink>WebRTC
Labels: M-57
Owner: hlundin@chromium.org
Status: Assigned (was: Untriaged)
Might be a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=659225, which is already fixed (waiting for clusterfuzz to re-run and verify).
Cc: tlegrand@chromium.org
No, this is not a duplicate but a new issue.
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 22 2016

Labels: -Restrict-View-EditIssue
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
Cc: hlundin@chromium.org kwiberg@chromium.org
Owner: ivoc@chromium.org
Project Member

Comment 7 by bugdroid1@chromium.org, Dec 13 2016

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

commit 03392d0047f8af9664395595150b95cb4fb9630c
Author: ivoc <ivoc@webrtc.org>
Date: Tue Dec 13 09:05:27 2016

Fix for negative shift value in NetEq.

BUG= chromium:667028 

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

[modify] https://crrev.com/03392d0047f8af9664395595150b95cb4fb9630c/webrtc/modules/audio_coding/neteq/normal.cc

Project Member

Comment 8 by ClusterFuzz, Dec 15 2016

ClusterFuzz has detected this issue as fixed in range 438480:438523.

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

Fuzzer: libfuzzer_neteq_rtp_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  webrtc::Normal::Process
  webrtc::NetEqImpl::DoNormal
  webrtc::NetEqImpl::GetAudioInternal
  
Regressed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=432467:432520
Fixed: https://cluster-fuzz.appspot.com/revisions?job=libfuzzer_chrome_ubsan&range=438480:438523

Minimized Testcase (0.21 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97IOV_wno37tCOPCtXH3psh2VmCMBS8udAIluYn0_Q-UGsjL_ZDmU72Cxo3338fwezK_ON0eZAneeoM6YtehoGmo1q-WlMEKO0rnrH_Q5kRsRbjK-WK8nm0i3AGYgJB7ElJaz4vGwZBIOCz37KpPqjgWlYuUA?testcase_id=4895682210299904

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.
Project Member

Comment 9 by ClusterFuzz, Dec 15 2016

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 4895682210299904 is verified as fixed, so closing issue.

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

Sign in to add a comment