[ 
https://issues.apache.org/jira/browse/GUACAMOLE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jumper resolved GUACAMOLE-424.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.15-incubating

> VNC client segfaults if provided password is incorrect
> ------------------------------------------------------
>
>                 Key: GUACAMOLE-424
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-424
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-server
>    Affects Versions: 0.9.13-incubating
>         Environment: VM has installed TightVNC server. 
> Guacmole server (guacd) installed using steps from here 
> (https://guacamole.incubator.apache.org/doc/gug/installing-guacamole.html)
> Guacmole client behind tomcat7
> Gucamole client has a postgresql database extension for dynamic user 
> authentication.
> Remote protocol - VNC
>            Reporter: Ivaylo Petkov Tsankov
>             Fix For: 0.9.15-incubating
>
>         Attachments: Screenshot from 2017-10-25 12-34-19.png, Screenshot from 
> 2017-10-25 12-34-22.png, failed_catalina.txt, failed_syslog.txt, 
> working_catalina.txt, working_syslog.txt
>
>
> Everything works ok with connections which match the remote vnc password of 
> the TightVNC server.
> The issue happens when there is a connection in guacmole-client which does 
> not match the remote VNC password of the TightVNC. When I attempt to connect 
> over this connection, the guacd failed with segfault.
> Here are guacd logs from the issue:
> {code:none}
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: VNC server supports protocol 
> version 3.8 (viewer 3.8)
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: We have 1 security types to read
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: 0) Received security type 2
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: Selecting security type 2 (0/1 
> in the list)
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: Selected Security Scheme 2
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: VNC connection failed: password 
> check failed!
> Oct 13 16:15:01 ip-172-31-18-56 guacd[13924]: Unable to connect to VNC server.
> Oct 13 16:15:02 ip-172-31-18-56 guacd[13730]: User is not responding.
> Oct 13 16:15:02 ip-172-31-18-56 kernel: [81568.417106] guacd[13733]: segfault 
> at 10 ip 00007f54edf56e62 sp 00007f54a37fdd50 error 4 in 
> libguac-client-vnc.so.0.0.0[7f54edf4e000+13000]
> Oct 13 16:15:02 ip-172-31-18-56 guacd[5325]: Connection 
> "$ee148c21-83b7-4e70-9051-c29b51a06c56" removed.
> Oct 13 16:15:03 ip-172-31-18-56 guacd[13744]: User is not responding.
> Oct 13 16:15:03 ip-172-31-18-56 kernel: [81569.081782] guacd[13747]: segfault 
> at 10 ip 00007f54edf56e62 sp 00007f54df7fdd50 error 4 in 
> libguac-client-vnc.so.0.0.0[7f54edf4e000+13000]
> Oct 13 16:15:03 ip-172-31-18-56 guacd[5325]: Connection 
> "$423ac38c-9dfe-4100-b2c6-bf83669aa76a" removed.
> Oct 13 16:15:04 ip-172-31-18-56 guacd[13762]: User is not responding.
> Oct 13 16:15:04 ip-172-31-18-56 kernel: [81569.985579] guacd[13765]: segfault 
> at 10 ip 00007f54dc5ece62 sp 00007f54ed960d50 error 4 in libguac-client-v
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to