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

Issue 748856 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
please use my google.com address
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 0
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in mojo::edk::ChannelPosix::WriteNoLock

Project Member Reported by ClusterFuzz, Jul 26 2017

Issue description

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  mojo::edk::ChannelPosix::WriteNoLock
  mojo::edk::ChannelPosix::Write
  mojo::edk::NodeChannel::SendChannelMessage
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489319:489347

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


Issue filed automatically.

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

Comment 1 by sheriffbot@chromium.org, Jul 26 2017

Labels: M-61
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 26 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 3 by sheriffbot@chromium.org, Jul 26 2017

Labels: Pri-1

Comment 4 by vakh@chromium.org, Jul 26 2017

Components: Internals>Mojo
Owner: roc...@chromium.org
Status: Assigned (was: Untriaged)
(Security Sheriff Triage)
rockot@-- this seems to have been caused by https://chromium-review.googlesource.com/584038 because that's the only mojo related CL in the regression range.
If you aren't the right owner, please help find them or mark the bug as Untriaged.
Cc: roc...@chromium.org
 Issue 749111  has been merged into this issue.
Cc: -roc...@chromium.org infe...@chromium.org
Labels: -Pri-1 Pri-0
This is Pri-0, crashing MSAN builds on startup and blocking fuzzing. Please fix soon or revert CL for now.

Comment 7 by roc...@chromium.org, Jul 26 2017

Status: Fixed (was: Assigned)
The CL has already been reverted.
Project Member

Comment 8 by ClusterFuzz, Jul 26 2017

Labels: OS-Mac
Project Member

Comment 9 by ClusterFuzz, Jul 27 2017

ClusterFuzz has detected this issue as fixed in range 489609:489658.

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

Fuzzer: inferno_layout_test_unmodified
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  mojo::edk::ChannelPosix::WriteNoLock
  mojo::edk::ChannelPosix::Write
  mojo::edk::NodeChannel::SendChannelMessage
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489319:489347
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=489609:489658

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


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 10 by ClusterFuzz, Jul 27 2017

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

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

Comment 11 by sheriffbot@chromium.org, Jul 27 2017

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

Comment 12 by sheriffbot@chromium.org, Nov 2 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