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

Issue 855830 link

Starred by 1 user
Status: Assigned
Owner:
kwiberg@chromium.org
Cc:
█ mflodman@webrtc.org
henrika@webrtc.org
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in WebRtcIlbcfix_Smooth

Project Member Reported by ClusterFuzz, Jun 23 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5125936987766784

Fuzzer: libFuzzer_audio_decoder_ilbc_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  WebRtcIlbcfix_Smooth
  WebRtcIlbcfix_Enhancer
  WebRtcIlbcfix_EnhancerInterface
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=396407:396452

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5125936987766784

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jun 23 2018

Cc: kwiberg@webrtc.org mflodman@webrtc.org henrika@webrtc.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 2 by henrika@chromium.org, Jun 25 2018

Cc: -kwiberg@webrtc.org
Owner: kwiberg@chromium.org
Status: Assigned (was: Untriaged)
https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+/dbb09094d88a6c1364a679df7103c14390f8a80b is the range of WebRTC changes and it touches iLBC.
Project Member

Comment 3 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 5125936987766784 appears to be flaky, updating reproducibility label.

Comment 4 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.

Comment 5 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
►

Sign in to add a comment