Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 682807 - sssd_nss core dumps with certain lookups
sssd_nss core dumps with certain lookups
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd (Show other bugs)
6.1
All Linux
high Severity high
: rc
: ---
Assigned To: Stephen Gallagher
Chandrasekar Kannan
:
Depends On:
Blocks: 682808
  Show dependency treegraph
 
Reported: 2011-03-07 11:05 EST by Guil Barros
Modified: 2015-01-04 18:46 EST (History)
7 users (show)

See Also:
Fixed In Version: sssd-1.5.1-11.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 682808 (view as bug list)
Environment:
Last Closed: 2011-05-19 07:40:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0560 normal SHIPPED_LIVE Low: sssd security, bug fix, and enhancement update 2011-05-19 07:38:17 EDT

  None (edit)
Description Guil Barros 2011-03-07 11:05:25 EST
Description of problem:
sssd_nss is segfaulting with certain netgroups lookups when using sudo.


Version-Release number of selected component (if applicable):
sssd-1.5.1-5.el6.x86_64
libdhash-0.4.2-6.el6.x86_64

How reproducible:
always?

Steps to Reproduce:
unknown trigger

# time sudo -l
Matching Defaults entries for root on this host:
always_set_home, env_reset, listpw=always, logfile=/var/log/sudo.log, logfile=/var/adm/sudo.log, always_set_home

Runas and Command-specific defaults for root:

User root may run the following commands on this host:
(ALL) ALL
(root) (ALL) ALL

real 0m16.969s
user 0m0.016s
sys 0m0.116s 

  
Actual results:
Syslog message: KERN.INFO: Mar  3 12:21:25 <host> kernel: sssd_nss[3002]: segfault at 0 ip 00000033bea00a5c sp 00007fff1f42e738 error 4 in libdhash.so.1.0.0[33bea00000+3000]


Expected results:
no segfault and sudo return in 1~2s
Comment 4 Stephen Gallagher 2011-03-07 11:10:33 EST
Tracked upstream by https://fedorahosted.org/sssd/ticket/817
Comment 6 Kaushik Banerjee 2011-04-29 14:47:17 EDT
In 1.5.1-10:
"getent -s sss netgroup non-existant-group" has sssd_nss crashing at the end of cache lifetime.

In 1.5.1-32:
"getent -s sss netgroup non-existant-group" doesn't crash sssd at the end of cache lifetime anymore.


Verified in version:
# rpm -qi sssd | head
Name        : sssd                         Relocations: (not relocatable)
Version     : 1.5.1                             Vendor: Red Hat, Inc.
Release     : 32.el6                        Build Date: Fri 29 Apr 2011 09:24:02 PM IST
Install Date: Fri 29 Apr 2011 11:49:07 PM IST      Build Host: hs20-bc2-4.build.redhat.com
Group       : Applications/System           Source RPM: sssd-1.5.1-32.el6.src.rpm
Size        : 3464087                          License: GPLv3+
Signature   : (none)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://fedorahosted.org/sssd/
Summary     : System Security Services Daemon
Comment 7 errata-xmlrpc 2011-05-19 07:40:29 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0560.html
Comment 8 errata-xmlrpc 2011-05-19 09:09:47 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2011-0560.html

Note You need to log in before you can comment on or make changes to this bug.