Bug 751314 - SSSD does not sanitize broken memberUID correctly
SSSD does not sanitize broken memberUID correctly
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Stephen Gallagher
Depends On:
  Show dependency treegraph
Reported: 2011-11-04 06:03 EDT by Jakub Hrozek
Modified: 2011-11-14 13:31 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
When a group contains certain incorrect multi-valued memberUID values, SSSD fails to sanitize the values properly. The memberUID value should only contain one username. As a result, SSSD creates incorrect users, using the broken memberUID values as their usernames. This, for example, causes problems during cache indexing.
Story Points: ---
Clone Of:
Last Closed: 2011-11-14 13:31:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jakub Hrozek 2011-11-04 06:03:26 EDT
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):

How reproducible:

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.
Comment 1 Jakub Hrozek 2011-11-04 06:05:45 EDT
Upstream ticket:
Comment 3 Jakub Hrozek 2011-11-04 06:20:32 EDT
Too late for 6.2. We agreed to document this issue in release notes.

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