Bug 712983

Summary: Segmentation fault in libgssglue
Product: Red Hat Enterprise Linux 6 Reporter: sadekok
Component: libgssglueAssignee: Steve Dickson <steved>
Status: CLOSED DUPLICATE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: high    
Version: 6.1CC: ddumas, ebenes, zmraz
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-11 16:48:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Stack Trace none

Description sadekok 2011-06-13 19:39:18 UTC
Created attachment 504529 [details]
Stack Trace

Description of problem:
When trying to connect to Kerberos Secure NFS, rpc.gssd fails when libgssglue segfaults.  Kerberos Server is an Active Directory 2008 server.

Version-Release number of selected component (if applicable):
nfs-utils 1.1.2.3-7
Kerberos 1.9-9

How reproducible:
Consistent from machine to machine with our configuration.

Steps to Reproduce:
1. Setup a kerberos principal nfs/fqdn encrypted in des-cbc-md5
2. Try mount a kerberosized NFS share
3.
  
Actual results:
rpc.gssd service fails with the log messages:

rpc.gssd[1526]: creating context using fsuid 0 (save_uid 0)
kernel: rpc.gssd[1526]: segfault at 1 ip 00007fb739da17ae sp 00007ffff7035118 error 4 in libgssglue.so.1.0.0[7fb739d9e000+9000]


Expected results:
No errors and and able to browse the root directory of the NFS share

Additional info:
It worked without issue on RHEL 5.5 and earlier.

Stack Trace is Attached

Comment 2 RHEL Program Management 2011-07-06 01:32:31 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 3 Steve Dickson 2011-09-14 19:22:59 UTC
The following patch fixes the problem:

commit 2e4a7e9b50a641dc8640a5dd911ee4a2f0b2c073
Author: Steve Dickson <steved>
Date:   Tue Apr 19 12:31:30 2011 -0400

    rpc.svcgssd: Segmentation fault on error
    
    Commit 544ed73d introduced a regression that caused
    rpc.svcgssd to seg fault on "Wrong principal in request"
    errors in gss_accept_sec_context()
    
    Signed-off-by: Steve Dickson <steved>

diff --git a/utils/gssd/gss_util.c b/utils/gssd/gss_util.c
index ca27d61..0e327b0 100644
--- a/utils/gssd/gss_util.c
+++ b/utils/gssd/gss_util.c
@@ -252,7 +252,8 @@ display_status_2(char *m, u_int32_t major, u_int32_t minor, const gss_OID mech)
 
 	if (major == GSS_S_CREDENTIALS_EXPIRED)
 		msg_verbosity = 1;
-	printerr(msg_verbosity, "ERROR: GSS-API: error in %s(): %s (%s) - %s(%s)\n",
+
+	printerr(msg_verbosity, "ERROR: GSS-API: error in %s(): %s (%s) - %s\n",
 		 m, gss_display_error(major), maj, min);
 
 	if (maj_gss_buf.length != 0)

Comment 4 Steve Dickson 2011-09-15 18:14:08 UTC
(In reply to comment #0)
> Created attachment 504529 [details]
> Stack Trace
> 
> Description of problem:
> When trying to connect to Kerberos Secure NFS, rpc.gssd fails when libgssglue
> segfaults.  Kerberos Server is an Active Directory 2008 server.
> 
> Version-Release number of selected component (if applicable):
> nfs-utils 1.1.2.3-7
> Kerberos 1.9-9
What version of libgssglue are you using?

Comment 6 sadekok 2011-10-07 19:06:32 UTC
libgssglue v 0.1 was used, but the issue was fixed with the nfs-utils 1.1.2.3-8 release in Bug 720479.

Comment 7 Steve Dickson 2011-10-11 16:48:11 UTC

*** This bug has been marked as a duplicate of bug 720479 ***