New issue
Advanced search Search tips

Issue 701754 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security

Blocking:
issue 698865



Sign in to add a comment

Use-of-uninitialized-value in decode_eld_specific_config

Project Member Reported by ClusterFuzz, Mar 15 2017

Issue description

Comment 1 by tsepez@chromium.org, Mar 15 2017

Owner: dalecur...@chromium.org
Status: ExternalDependency (was: Untriaged)
Assigning to dalecurtis@ per OWNERS file.  Please re-assign as appropriate.
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 16 2017

Labels: M-58
Project Member

Comment 3 by sheriffbot@chromium.org, Mar 16 2017

Labels: ReleaseBlock-Beta
This issue is a security regression. If you are not able to fix this quickly, please revert the change that introduced it.

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

Comment 4 by sheriffbot@chromium.org, Mar 16 2017

Labels: Pri-1
Labels: -ReleaseBlock-Beta ARC-ReleaseBlock-Stable
Owner: tguilbert@chromium.org
Status: Assigned (was: ExternalDependency)
Non-regression, just a newly found issue. But +RBS, over to tguilbert@ for review to see if there's a fix to land.

Comment 6 by tsepez@chromium.org, Mar 16 2017

Components: Internals>Media
Project Member

Comment 7 by sheriffbot@chromium.org, Mar 17 2017

Labels: -Security_Impact-Head Security_Impact-Beta
Project Member

Comment 8 by sheriffbot@chromium.org, Mar 17 2017

Labels: ReleaseBlock-Stable
Blocking: 698865
Project Member

Comment 10 by sheriffbot@chromium.org, Apr 4 2017

tguilbert: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
A friendly reminder that M58 Stable is launch is coming soon (less than 2 weeks)! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!
Labels: -Security_Impact-Beta -ReleaseBlock-Stable Security_Impact-Stable
Project Member

Comment 13 by bugdroid1@chromium.org, Apr 12 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/third_party/ffmpeg/+/28a5cdde5c32bcf66715343c10f74e85713f7aaf

commit 28a5cdde5c32bcf66715343c10f74e85713f7aaf
Author: Thomas Guilbert <tguilbert@chromium.org>
Date: Wed Apr 12 00:45:40 2017

avformat/oggparseogm: Check available data before reading global header

Fixes use of uninitialized data

Found-by: Thomas Guilbert <tguilbert@google.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
(cherry picked from commit 170d864d2c508ca8111b1d108e1e964007dab712)

Bug:700673,  700690 ,  701754 

Change-Id: I90795c2fe9e3c2f29f53f7a5f58339c3e7ca05f6
Reviewed-on: https://chromium-review.googlesource.com/475027
Reviewed-by: Matthew Wolenetz <wolenetz@chromium.org>

[modify] https://crrev.com/28a5cdde5c32bcf66715343c10f74e85713f7aaf/libavformat/oggparseogm.c

Project Member

Comment 14 by ClusterFuzz, Apr 12 2017

ClusterFuzz has detected this issue as fixed in range 463886:463918.

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

Fuzzer: libfuzzer_media_pipeline_integration_fuzzer
Job Type: libfuzzer_chrome_msan
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  decode_eld_specific_config
  decode_audio_specific_config_gb
  decode_audio_specific_config
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=423366:423427
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_msan&range=463886:463918

Reproducer Testcase: https://clusterfuzz.com/download/AMIfv94ijJ88fWJLBBvX8UhJ-p3ibbWjThNmaXiC51eAMtVNZlaCxQhqYhIxALC3ZjMeBK0djRynVZlMUwGlmFEiHo3_6M4mzAaEkdw-FgiIf0duTn3k9ZAWLUZ3Rwi-7-No44FtF_fYsRX_-ZQWLHsgVDo_aIHCsFsIBG9Lq2iXM6Q2CSgecHwMxThVu7sl-P0G8U6LRPjMlZlV9rxxLaqxHwf4uo2bFMiNOh3-eE6-vqYlYnQxR4HWmV0MwyhEKTRv8i_n2VdZ_yfjP-SV4FKhLXJUwtUbZ4wMqbYVmSBi0UHdXBewase74_BklOTBlUGnY3qIsI748r-xAbZpvC_2SXLsY2v8fbOpdTbD7V7OpTpF1ynAgkDHMPuFE0DQM7G1JvX2ZislqHnLETzrVUhYBn3tcLCp7Q?testcase_id=4740714023092224


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 15 by ClusterFuzz, Apr 12 2017

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

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

Comment 16 by sheriffbot@chromium.org, Apr 12 2017

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -M-58 M-59
Labels: Release-0-M59
Project Member

Comment 19 by sheriffbot@chromium.org, Jul 19 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

Sign in to add a comment