801533 – sssd_be crashes when resolving non-trivial nested group structure

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 801533 - sssd_be crashes when resolving non-trivial nested group structure

Summary: sssd_be crashes when resolving non-trivial nested group structure

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	sssd
Sub Component:
Version:	6.3
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Stephen Gallagher
QA Contact:	IDM QE LIST
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2012-03-08 18:35 UTC by Jakub Hrozek
Modified:	2020-05-02 16:47 UTC (History)
CC List:	4 users (show)
Fixed In Version:	sssd-1.8.0-12.el6
Doc Type:	Bug Fix
Doc Text:	Cause: When SSSD was resolving a complex group structure during an initgroups operation, it used a wrong counter and could have accessed random memory Consequence: The random memory access crashed the sssd_be process Fix: SSSD now uses the correct group counter Result: SSSD processes nested group structures correctly
Clone Of:
Environment:
Last Closed:	2012-06-20 11:55:51 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Github	SSSD sssd issues 2285	0	None	None	None	2020-05-02 16:47:53 UTC
Red Hat Product Errata	RHBA-2012:0747	0	normal	SHIPPED_LIVE	sssd bug fix and enhancement update	2012-06-19 19:31:43 UTC

Description Jakub Hrozek 2012-03-08 18:35:20 UTC

Description of problem:
When SSSD is resolving memberships in a slightly complex group structure, the back end can crash. This is due to bad counter of parent groups in a nested group level.

Version-Release number of selected component (if applicable):
1.8.0

How reproducible:
always

Steps to Reproduce:
1. Configure a nested group structure that looks like this:

user --- A    -- BA --- BAA
  \          /     \
   \        /       \
     --- B -         -- BAB
            \
             \
              -- BB --- BBA
                   \
                    \
                     -- BBB

2. id user
  
Actual results:
segfault

Expected results:
id runs correctly

Additional info:
Reported by Bojan Smojver in https://bugzilla.redhat.com/show_bug.cgi?id=743133#c28

Comment 1 Jakub Hrozek 2012-03-08 18:38:02 UTC

Upstream ticket:
https://fedorahosted.org/sssd/ticket/1243

Comment 5 Jakub Hrozek 2012-04-03 18:44:36 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: When SSSD was resolving a complex group structure during an initgroups operation, it used a wrong counter and could have accessed random memory

Consequence: The random memory access crashed the sssd_be process

Fix: SSSD now uses the correct group counter

Result: SSSD processes nested group structures correctly

Comment 6 Amith 2012-04-11 11:27:39 UTC

Verified on sssd-1.8.0-22.el6.x86_64.

The output for the associated beaker automation script is given below:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: Verify BZ release ticket #364: sssd_be crashes when resolving non-trivial nested group structure
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: Running '/usr/bin/ldapadd -x -D cn=Manager,dc=example,dc=com -w Secret123 -H ldap://hubcap.lab.eng.pnq.redhat.com -f /tmp/tempuser.ldif > /dev/null 2>&1'
:: [   PASS   ] :: Running '/usr/bin/ldapadd -x -D cn=Manager,dc=example,dc=com -w Secret123 -H ldap://hubcap.lab.eng.pnq.redhat.com -f /tmp/tempgroup.ldif > /dev/null 2>&1'
:: [   PASS   ] :: Running '/usr/bin/id tempuser &'
:: [   PASS   ] :: Running '/bin/sleep 30s'
:: [   PASS   ] :: File '/tmp/templog' should not contain 'segfault at'
:: [   PASS   ] :: Running '/usr/bin/ldapmodify -x -D cn=Manager,dc=example,dc=com -w Secret123 -H ldap://hubcap.lab.eng.pnq.redhat.com -f /tmp/deluser.ldif > /dev/null 2>&1'
:: [   PASS   ] :: Running '/usr/bin/ldapmodify -x -D cn=Manager,dc=example,dc=com -w Secret123 -H ldap://hubcap.lab.eng.pnq.redhat.com -f /tmp/delgroup.ldif > /dev/null 2>&1'
:: [   LOG    ] :: Duration: 1m 22s
:: [   LOG    ] :: Assertions: 16 good, 0 bad
:: [   PASS   ] :: RESULT: Verify BZ release ticket #364: sssd_be crashes when resolving non-trivial nested group structure

Comment 8 errata-xmlrpc 2012-06-20 11:55:51 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0747.html

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