New issue
Advanced search Search tips

Issue 735718 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in webrtc::FuzzAudioProcessing

Project Member Reported by ClusterFuzz, Jun 21 2017

Issue description

Detailed report: https://clusterfuzz.com/testcase?key=5581080769069056

Fuzzer: libFuzzer_audio_processing_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  webrtc::FuzzAudioProcessing
  webrtc::FuzzAudioProcessing
  webrtc::FuzzOneInput
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=481183:481216

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


Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: guidou@chromium.org
Components: Blink>WebRTC
Owner: aleloi@chromium.org
Status: Assigned (was: Untriaged)
aleloi: can you please take a look at this?

Comment 2 by aleloi@chromium.org, Jun 22 2017

Cc: hlundin@chromium.org
Components: -Blink>WebRTC Blink>WebRTC>Audio
Labels: M-61
Project Member

Comment 4 by sheriffbot@chromium.org, Jun 22 2017

Labels: ReleaseBlock-Stable
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
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 22 2017

Labels: Pri-1

Comment 6 by aleloi@chromium.org, Jun 22 2017

Status: Fixed (was: Assigned)
Fixed in https://chromium-review.googlesource.com/c/544937/. Which for some reason didn't get linked here.
Labels: -Security_Severity-Medium -ReleaseBlock-Stable Security_Severity-Low ReleaseBlock-NA
Changing to low severity and ReleaseBlock-NA since this is an issue in a tool, not in the Chrome product.
Project Member

Comment 8 by sheriffbot@chromium.org, Jun 23 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Project Member

Comment 9 by ClusterFuzz, Jun 28 2017

ClusterFuzz has detected this issue as fixed in range 481600:482746.

Detailed report: https://clusterfuzz.com/testcase?key=5581080769069056

Fuzzer: libFuzzer_audio_processing_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  webrtc::FuzzAudioProcessing
  webrtc::FuzzAudioProcessing
  webrtc::FuzzOneInput
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=481183:481216
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=481600:482746

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


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 10 by sheriffbot@chromium.org, Sep 29 2017

Labels: -Restrict-View-SecurityNotify allpublic
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
Project Member

Comment 11 by sheriffbot@chromium.org, Jul 28

Labels: -Pri-1 Pri-2

Sign in to add a comment