First published: Tue May 27 2014(Updated: )
It was reported [1] that SSSD improperly expanded group membership when it encountered a non-POSIX group in the group membership chain. For instance: user -> posix_group1 -> non_posix_group -> posix_group2 With the group memberships noted above, SSSD should include the user as a member of both posix_group1 and posix_group2, however due to the position of the non-POSIX group, SSSD halts processing at it and never reaches posix_group2, leaving the user as a member of posix_group1 and not posix_group2. SSSD has the capability to set a 'deny' ACL for both users and groups, so in a situation like that illustrated above, if posix_group2 was present in a 'deny' ACL, the user would be granted access because they are not shown as having membership in the denied group. This could grant unintended access to certain users in an environment where non-POSIX groups are used in addition to POSIX groups. There is currently no patch to correct this issue. [1] <a href="https://lists.fedorahosted.org/pipermail/sssd-devel/2014-May/019495.html">https://lists.fedorahosted.org/pipermail/sssd-devel/2014-May/019495.html</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Fedoraproject Sssd | =1.11.6 | |
Redhat Enterprise Linux | =5 | |
Redhat Enterprise Linux | =6.0 | |
redhat/sssd | <1.11.7 | 1.11.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.