[
https://issues.apache.org/jira/browse/GUACAMOLE-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17078499#comment-17078499
]
Nick Couchman commented on GUACAMOLE-1017:
------------------------------------------
[~mjharvey]: Can you provide a full stack trace? This looks like the segfault
is likely upstream in the Pango library, or perhaps even in libc, but a stack
trace would be good.
Also, while I agree it is something that you reasonably easily reproduce by
"cat /dev/urandom", I would say that this is not something that people are
likely to do on a frequent basis. Is there some other precipitating event
you've encountered that would be similar to "cat /dev/urandom" that makes this
something likely to be hit by a large number of users?
> Invalid UTF-8 string passed to pango_layout_set_text() -- leading to guacd
> segfault
> -----------------------------------------------------------------------------------
>
> Key: GUACAMOLE-1017
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1017
> Project: Guacamole
> Issue Type: Bug
> Components: guacd
> Environment: CentOS 7, guacd 1.1.0-1 from EPEL
> rpm -qa | grep guac
> guacd-1.1.0-1.el7.x86_64
> libguac-client-vnc-1.1.0-1.el7.x86_64
> libguac-1.1.0-1.el7.x86_64
> libguac-client-rdp-1.1.0-1.el7.x86_64
> libguac-client-ssh-1.1.0-1.el7.x86_64
> Reporter: M J Harvey
> Priority: Minor
>
> Hi,
> Probabilistic reproducible segfault of guacd:
> * Installed guacd and guacamole from EPEL on a CentOS 7.7.1908 system.
> * Configure an SSH connection type.
> * Establish guacamole session to SSH server
> * Do "cat /dev/urandom" to generate garbage.
> * {{Observe /var/log/messages on the guacd server, you'll see frequent logs
> of }}{{"Invalid UTF-8 string passed to pango_layout_set_text()"}}
> * {{Session will pretty rapidly terminate. About 20% of the time this is an
> uncontrolled segfault from libc}}
> {{guacd[7688]: segfault at 7f3ea6177ff0 ip 00007f3ea3cb2b1d sp
> 00007f3e9d902ab8 error 4 in libc-2.17.so[7f3ea3b57000+1c3000]}}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)