New issue
Advanced search Search tips

Issue 853421 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Use-of-uninitialized-value in void base::Pickle::WriteBytesStatic<4ul>

Project Member Reported by ClusterFuzz, Jun 16 2018

Issue description

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  void base::Pickle::WriteBytesStatic<4ul>
  IPC::ParamTraits<gpu::FlushParams>::Write
  IPC::MessageT<GpuChannelMsg_FlushCommandBuffers_Meta, std::__1::tuple<std::__1::
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=567493:567494

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

Issue filed automatically.

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

Comment 1 by ClusterFuzz, Jun 16 2018

Labels: Fuzz-Blocker ReleaseBlock-Beta M-69
This crash occurs very frequently on linux platform and is likely preventing the fuzzer lcamtuf_cross_fuzz from making much progress. Fixing this will allow more bugs to be found.

Marking this bug as a blocker for next Beta release.

If this is incorrect, please add ClusterFuzz-Wrong label and remove the ReleaseBlock-Beta label.
Project Member

Comment 2 by ClusterFuzz, Jun 16 2018

ClusterFuzz has detected this issue as fixed in range 567630:567631.

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

Fuzzer: lcamtuf_cross_fuzz
Job Type: linux_msan_content_shell_drt
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  void base::Pickle::WriteBytesStatic<4ul>
  IPC::ParamTraits<gpu::FlushParams>::Write
  IPC::MessageT<GpuChannelMsg_FlushCommandBuffers_Meta, std::__1::tuple<std::__1::
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=567493:567494
Fixed: https://clusterfuzz.com/revisions?job=linux_msan_content_shell_drt&range=567630:567631

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

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 3 by ClusterFuzz, Jun 16 2018

Labels: ClusterFuzz-Verified
Status: Verified (was: Untriaged)
ClusterFuzz testcase 5346466932195328 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 4 by sheriffbot@chromium.org, Jun 16 2018

Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Labels: -ReleaseBlock-Beta
Components: Internals
Project Member

Comment 7 by sheriffbot@chromium.org, Jul 28

Labels: Pri-1
Project Member

Comment 8 by sheriffbot@chromium.org, Sep 22

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