xfreerdp crashed with SIGSEGV in X509_get_issuer_name()

Bug #1116999 reported by Dana Goyette
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
freerdp (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

If I try to connect to my workplace's RDP server (64-bit Server 2008 R2), xfreerdp crashes.
The same is true of remmina, but I figured xfreerdp should be simpler to backtrace.

Steps to reproduce:
1. run xfreerdp winrd-ng.nominum.com
2. Respond to password prompt with enter -- it doesn't matter.
3. Crash.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: freerdp-x11 1.0.1-1ubuntu7
ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2
Uname: Linux 3.5.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Tue Feb 5 22:09:01 2013
ExecutablePath: /usr/bin/xfreerdp
InstallationDate: Installed on 2013-01-11 (25 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MarkForUpload: True
ProcCmdline: xfreerdp winrd-ng
ProcCwd: /home/dana/Documents
RetraceOutdatedPackages: outdated debug symbol package for libc-bin: package version 2.15-0ubuntu20 dbgsym version 2.15-0ubuntu20.1
Signal: 11
SourcePackage: freerdp
StacktraceTop:
 X509_get_issuer_name (a=0x7f4300000019) at x509_cmp.c:133
 crypto_cert_issuer () from /tmp/tmpRsJ0tM/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
 tls_verify_certificate () from /tmp/tmpRsJ0tM/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
 credssp_get_public_key () from /tmp/tmpRsJ0tM/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
 credssp_authenticate () from /tmp/tmpRsJ0tM/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
Title: xfreerdp crashed with SIGSEGV in X509_get_issuer_name()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo wireshark

Revision history for this message
Dana Goyette (danagoyette) wrote :
description: updated
Revision history for this message
Dana Goyette (danagoyette) wrote :

StacktraceTop:
 X509_get_issuer_name () from /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
 crypto_cert_issuer () from /usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
 tls_verify_certificate () from /usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
 credssp_get_public_key () from /usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0
 credssp_authenticate () from /usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0

Revision history for this message
Dana Goyette (danagoyette) wrote : Stacktrace.txt
Revision history for this message
Dana Goyette (danagoyette) wrote : StacktraceSource.txt
Revision history for this message
Dana Goyette (danagoyette) wrote : ThreadStacktrace.txt
Revision history for this message
Dana Goyette (danagoyette) wrote :

Those extra attachments seem to be from me trying to apport retrace... I ran into this:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1055110
...and then...
W: Unable to read /tmp/tmprlmkUC/Ubuntu 12.10/apt/etc/apt/apt.conf.d/ - DirectoryExists (2: No such file or directory)
W: Unable to read /tmp/tmprlmkUC/Ubuntu 12.10/apt/etc/apt/sources.list.d/ - DirectoryExists (2: No such file or directory)
W: Unable to read /tmp/tmprlmkUC/Ubuntu 12.10/apt/etc/apt/sources.list - RealFileExists (2: No such file or directory)
W: Unable to read /tmp/tmprlmkUC/Ubuntu 12.10/apt/etc/apt/preferences.d/ - DirectoryExists (2: No such file or directory)
E: You must put some 'source' URIs in your sources.list

Right now, it looks like the only private information is the server name.
For comparison, I tried a different server, and did not get the same crash.

information type: Private → Private Security
information type: Private Security → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in freerdp (Ubuntu):
status: New → Confirmed
tags: removed: need-amd64-retrace
Revision history for this message
msaxl (saxl) wrote :

I hit this bug if I assign a cerificate to the ts server that was signed by a sub-ca.

I cannot say if a certificate signed by a root ca would work, but selfsigned certificates seem to work

Revision history for this message
Till W. (tillw.) wrote :

In case you need a server to reproduce the bug with, try connecting to uniapps.uni-rostock.de with arbitrary domain name, username and password.

I am rather sure that this server uses a cert signed by an itermediate CA (because they do it for other services such as HTTP as well.) I tried to verify using openssl's s_client tool:

# openssl s_client -connect uniapps.uni-rostock.de:3389
[…]
Certificate chain
 0 s:/C=DE/ST=Mecklenburg-Vorpommern/L=Rostock/O=Universitaet Rostock/OU=ITMZ/CN=rds1.uni-rostock.de
   i:/C=DE/O=Universitaet Rostock/OU=Rechenzentrum/CN=Uni Rostock CA - <email address hidden>
 1 s:/C=DE/O=Universitaet Rostock/OU=Rechenzentrum/CN=Uni Rostock CA - <email address hidden>
   i:/C=DE/O=DFN-Verein/OU=DFN-PKI/CN=DFN-Verein PCA Global - G01
 2 s:/C=DE/O=DFN-Verein/OU=DFN-PKI/CN=DFN-Verein PCA Global - G01
   i:/C=DE/O=Deutsche Telekom AG/OU=T-TeleSec Trust Center/CN=Deutsche Telekom Root CA 2
[…]

Revision history for this message
Andreas (andreas-rabus) wrote :

Bug is alive. Again.
I wnat to connetc to my companies rdp server and all RDP programms (vinagre, remmina, xfreerdp) crash. (Gnome Ubuntu 14.10 )
Is it an SSL issue? And not related to RDP?
It used to work last month, but since a week (Poodle....) it crashes with the same symptoms.

Revision history for this message
axoin (axoin) wrote :

try using a more recent version of remmina (1.1.1 works for me, I had the same problem previously), there is a remmina ppa, see
https://launchpad.net/~remmina-ppa-team

Revision history for this message
Andreas (andreas-rabus) wrote :

The remmina version from the ppa (mentioned by @axoin in #11) doe not crash and asks to accept the certificate, then connects.
 So this is a workaround.

Only Problem is that this ppa breaks the vinagre rdp tool from the gnome team ppa (dependencies conflicts).
Let's hope its only this one tool...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.