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.

Description of problem:
When a group contains certain incorrect multivalued memberUID values, SSSD fails to sanitize the value properly. The memberUID value should contain one username, so SSSD creates fake users using the broken memberUID as their username. This causes problems during cache indexing, for example.

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

How reproducible:
always

Steps to Reproduce:
1. Create a group similar to this one:

dn: badmemberuid,ou=Groups,dc=example,dc=com
memberUid: userone,usertwo,userthree
gidNumber: 5418
cn: badmemberuid
objectClass: posixGroup
objectClass: top

2. getent group badmemberuid
3. ldbsearch -H /var/lib/sss/db/cache_example.com.ldb

Actual results:
The commas are not treated as special characters.

Expected results:
The commas are escaped with a '\' to sanitize them.

The DN should be sanitized and upgrades (which index the cache) should perform fine.

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

Too late for 6.2. We agreed to document this issue in release notes.