Impact
Under very specific conditions changes to a users groups may not have the expected results.
The specific conditions are:
- The file authentication backend is being used.
- The watch option is set to true.
- The refresh_interval is configured to a non-disabled value.
- The users groups are adjusted by an administrator.
- The user attempts to access a resource that their groups previously had access to but their new groups do not have access to.
When these conditions are met administrators may find the changes are not taken into account by access control for longer than expected periods. While this may not necessarily be a security vulnerability it's security-adjacent and because of the unexpected nature of it and our dedication to a security-first culture we feel it's important to make users aware of this behaviour utilizing a security advisory and the existence of a fix.
This:
- Can not have an Impact for Unauthenticated Users.
- Can not have an Impact for Configurations utilizing the LDAP Backend.
- Can not be directly or indirectly caused by a users or third parties actions.
Patches
This behaviour was identified after it was inadvertently fixed in the master branch during the multi-cookie domain rework (i.e. between feature releases). A patch for prior versions can be provided upon request. The fix was to ensure the details are updated regardless of backend, it was a small oversight in previous functionality which made refreshing ineffectual prior to v4.37.0.
Workarounds
Ensure you restart between user database changes.
References
References
ezrizhu Reporter
Impact
Under very specific conditions changes to a users groups may not have the expected results.
The specific conditions are:
When these conditions are met administrators may find the changes are not taken into account by access control for longer than expected periods. While this may not necessarily be a security vulnerability it's security-adjacent and because of the unexpected nature of it and our dedication to a security-first culture we feel it's important to make users aware of this behaviour utilizing a security advisory and the existence of a fix.
This:
Patches
This behaviour was identified after it was inadvertently fixed in the
masterbranch during the multi-cookie domain rework (i.e. between feature releases). A patch for prior versions can be provided upon request. The fix was to ensure the details are updated regardless of backend, it was a small oversight in previous functionality which made refreshing ineffectual prior to v4.37.0.Workarounds
Ensure you restart between user database changes.
References
References