New issue
Advanced search Search tips

Issue 875550 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug-Security



Sign in to add a comment

Use-of-uninitialized-value in _xcb_conn_wait

Project Member Reported by ClusterFuzz, Aug 18

Issue description

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

Fuzzer: ifratric-browserfuzzer-v3
Job Type: linux_msan_chrome
Platform Id: linux

Crash Type: Use-of-uninitialized-value
Crash Address: 
Crash State:
  _xcb_conn_wait
  xcb_writev
  _XSend
  
Sanitizer: memory (MSAN)

Recommended Security Severity: Medium

Regressed: https://clusterfuzz.com/revisions?job=linux_msan_chrome&range=582653:582655

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

Issue filed automatically.

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

Comment 1 by sheriffbot@chromium.org, Aug 18

Labels: Target-70 M-70
Project Member

Comment 2 by sheriffbot@chromium.org, Aug 18

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, Aug 18

Labels: Pri-1
Components: Internals>Services>Viz
Owner: sugoi@chromium.org
Status: Assigned (was: Untriaged)
sugoi: Looks like this might be related to crrev.com/c/1128207 which is in the regression range, can you take a look? Thanks.
Cc: infe...@chromium.org
This test is ran using "--use-gl=osmesa". It should be switched to using "--use-gl=swiftshader". I don't know where this command line argument comes from.


CCing inferno@ who might know where the command line argument comes from.
Status: WontFix (was: Assigned)
Testcase will persist having --use-gl=osmesa, so marking WontFix to close
Project Member

Comment 8 by ClusterFuzz, Sep 7

Labels: Needs-Feedback
ClusterFuzz testcase 5107981868597248 is still reproducing on tip-of-tree build (trunk).

If this testcase was not reproducible locally or unworkable, ignore this notification and we will file another bug soon with hopefully a better and workable testcase.

Otherwise, if this is not intended to be fixed (e.g. this is an intentional crash), please add ClusterFuzz-Ignore label to prevent future bug filing with similar crash stacktrace.
Project Member

Comment 9 by sheriffbot@chromium.org, Dec 8

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