CVE-2014-0249: Low severity Fedoraproject Sssd vulnerability
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 -> posixgroup1 -> nonposixgroup -> posixgroup2
With the group memberships noted above, SSSD should include the user as a member of both posixgroup1 and posixgroup2, however due to the position of the non-POSIX group, SSSD halts processing at it and never reaches posixgroup2, leaving the user as a member of posixgroup1 and not posixgroup2.
SSSD has the capability to set a 'deny' ACL for both users and groups, so in a situation like that illustrated above, if posixgroup2 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] https://lists.fedorahosted.org/pipermail/sssd-devel/2014-May/019495.html
Other sources
The System Security Services Daemon (SSSD) 1.11.6 does not properly identify group membership when a non-POSIX group is in a group membership chain, which allows local users to bypass access restrictions via unspecified vectors.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2014-0249?
CVE-2014-0249 has been classified as a moderate vulnerability due to improper group membership expansion in SSSD.
How do I fix CVE-2014-0249?
To fix CVE-2014-0249, update SSSD to version 1.11.7 or later.
Which software versions are affected by CVE-2014-0249?
CVE-2014-0249 affects SSSD versions prior to 1.11.7, including versions 1.11.6 and earlier.
What is SSSD and why is CVE-2014-0249 a concern?
SSSD, or System Security Services Daemon, is a service that provides access to identity and authentication resources, making CVE-2014-0249 a concern due to its potential impact on user group membership management.
Is there a workaround for CVE-2014-0249?
There are no recommended workarounds for CVE-2014-0249; updating to the fixed version is advised.