New issue
Advanced search Search tips

Issue 832493 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Oct 4
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Security



Sign in to add a comment

Crash in libX11.so.6

Project Member Reported by ClusterFuzz, Apr 13 2018

Issue description

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

Fuzzer: phoglund_webrtc_peerconnection
Job Type: linux_asan_chrome_chromeos
Platform Id: linux

Crash Type: UNKNOWN READ
Crash Address: 0x7f2c4fab3c00
Crash State:
  libX11.so.6
  
Sanitizer: address (ASAN)

Recommended Security Severity: Low

Regressed: https://clusterfuzz.com/revisions?job=linux_asan_chrome_chromeos&range=473029:473088

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

Additional requirements: Requires Gestures

Additional requirements: Requires HTTP

Issue filed automatically.

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

Comment 1 by sheriffbot@chromium.org, Apr 13 2018

Labels: Pri-2
Owner: jorgelo@chromium.org
Status: Assigned (was: Untriaged)
jorgelo - not much to go on.  Do you know of someone in chrome os to whom this should be assigned?  I'm not real clear on the breakdown between the chrome and chrome os parts of this one.
Chrome OS doesn't use X anymore, so I think this is an artifact of running the Chrome OS version of Chrome directly on Linux.
I.e. there's nothing to fix here if the crash was in libX11.
Status: ExternalDependency (was: Assigned)
Status: WontFix (was: ExternalDependency)
We haven't even filed anything with X so it's not like anything will ever happen for this bug.
Project Member

Comment 7 by ClusterFuzz, Oct 11

Labels: Needs-Feedback
ClusterFuzz testcase 5297483237031936 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 8 by sheriffbot@chromium.org, Jan 11

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