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

Issue 822819 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 823074
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in blink::LayoutCustom::AddChild

Project Member Reported by ClusterFuzz, Mar 16 2018

Issue description

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::LayoutCustom::AddChild
  blink::LayoutBlockFlow::CreateOrDestroyMultiColumnFlowThreadIfNeeded
  blink::LayoutBlockFlow::StyleDidChange
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=539921:539941

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
 
Project Member

Comment 1 by ClusterFuzz, Mar 16 2018

Components: Blink>Layout
Labels: Test-Predator-Auto-Components
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Mar 16 2018

Labels: Test-Predator-Auto-Owner
Owner: ikilpatrick@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://chromium.googlesource.com/chromium/src/+/1f9508a413a9234e7aa3504edbae538081200532 ([css-layout-api] Populate children, and pass into layout() function).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.

Comment 3 by est...@chromium.org, Mar 16 2018

Labels: M-66
Project Member

Comment 4 by sheriffbot@chromium.org, Mar 17 2018

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, Mar 17 2018

Labels: Pri-1
Project Member

Comment 6 by sheriffbot@chromium.org, Mar 31 2018

ikilpatrick: 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
Just a heads up, M66 Stable cut is on April 12th, 10 days away. This issue is marked as RB-Stable for 66. Please make sure to address this issue prior to stable cut. Thanks! 
Reminder: Please note that M66 Stable is only 7 days away. This bug has been marked as ReleaseBlock Stable for M66. So please take a look and appropriately address this bug. 

Comment 9 by awhalley@google.com, Apr 11 2018

Cc: mstensho@chromium.org atotic@chromium.org jstenback@chromium.org xiaoche...@chromium.org futhark@chromium.org
Mergedinto: 823074
Status: Duplicate (was: Assigned)
Problem disappears with https://chromium-review.googlesource.com/c/chromium/src/+/990780
Project Member

Comment 11 by ClusterFuzz, Apr 13 2018

ClusterFuzz has detected this issue as fixed in range 550146:550148.

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

Fuzzer: ochang_domfuzzer
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  blink::LayoutCustom::AddChild
  blink::LayoutBlockFlow::CreateOrDestroyMultiColumnFlowThreadIfNeeded
  blink::LayoutBlockFlow::StyleDidChange
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=539921:539941
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=550146:550148

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

See https://github.com/google/clusterfuzz-tools 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 12 by sheriffbot@chromium.org, Jul 20

Labels: -Restrict-View-SecurityTeam 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