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

yangguo -- if you are not the right person to own this, can you please help triage it better? Thanks.

Assigning to this week's sheriff.

mstarzinger: 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

Reassigning to this week's sheriff.

ClusterFuzz has detected this issue as fixed in range 589772:589773.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  v8::internal::Factory::NewNumber
  v8::internal::LookupIterator::FetchValue
  v8::internal::Object::GetProperty
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Fixed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=589772:589773

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

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.

ClusterFuzz testcase 4986854798262272 is verified as fixed, so closing issue as verified.

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

Looks like this was fixed by the chromite roll in https://chromium.googlesource.com/chromium/src/+/c62924a209ede743e5156632e3194d548df3ad92 - might we want to take this for M70?

This bug requires manual review: We are only 13 days from stable.
Please contact the milestone owner if you have questions.
Owners: benmason@(Android), kariahda@(iOS), geohsu@(ChromeOS), abdulsyed@(Desktop)

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

How safe is this merge overall?

Given the stage in the release, tracking for 71.

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