#1761 sssd_be crashes looking up members with groups outside the nesting limit
Closed: Fixed None Opened 8 years ago by jhrozek.

https://bugzilla.redhat.com/show_bug.cgi?id=894997 (Red Hat Enterprise Linux 6)

Created attachment 678136
LDIF used to upload users and groups to ldap server

Description of problem:
sssd_be crashes looking up members with groups outside the nesting limit

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

How reproducible:

Steps to Reproduce:
1. Use the attached ldif to add users and groups to the ldap server.
The structure is as follows:
Top:    Group1(member:nest_user1)
Mid:    Group2(member:nest_user2)
Lowest: Group3(member:nest_user3)

2. Add ldap_group_nesting_level = 1 in sssd.conf

3. # id nest_user3
uid=10297(nest_user3) gid=10002(Group_3) groups=10002(Group_3)

Actual results:
sssd_be crashes after id lookup is run. See attached backtrace.

Expected results:
sssd_be should not crash.

Additional info:
There is no crash with the following set of commands:
# id nest_user1; id nest_user3
uid=10299(nest_user1) gid=10000(Group_1) groups=10000(Group_1)
uid=10297(nest_user3) gid=10002(Group_3)
groups=10002(Group_3),10001(Group_2),10000(Group_1)  <= But Group1 and Group2
should not be displayed here.

Fields changed

blockedby: =>
blocking: =>
coverity: =>
design: =>
design_review: => 0
feature_milestone: =>
fedora_test_page: =>
owner: somebody => jhrozek
priority: major => blocker
selected: =>
status: new => assigned
testsupdated: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.4
patch: 0 => 1

resolution: => fixed
status: assigned => closed

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.4

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2803

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.