lemur: Authorization bypass due to default False config flags in permissions
In lemur/auth/permissions.py, `StrictRolePermission` and `AuthorityCreatorPermission` passed zero `Need`s to `flask_principal.Permission.__init__()` when config
What changed
In lemur/auth/permissions.py, `StrictRolePermission` and `AuthorityCreatorPermission` passed zero `Need`s to `flask_principal.Permission.__init__()` when config flags defaulted to `False`, causing `Permission.allows()` to return `True` for any authenticated identity.
Who it affects
All Lemur installations that did not explicitly set `ADMIN_ONLY_AUTHORITY_CREATION` or `LEMUR_STRICT_ROLE_ENFORCEMENT` to `True`. Users with only the `read-only` role can create root CAs, upload certificates, create/modify notifications, and create domains.
What to do today
Update Lemur to the fixed version where config flag defaults are changed to `True`. Ensure `ADMIN_ONLY_AUTHORITY_CREATION` and `LEMUR_STRICT_ROLE_ENFORCEMENT` are not set to `False` in your configuration.