Impact
Users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider.
Only deployments where LDAP servers are configured to allow unauthenticated binds (eg. default on Active Directory) are affected.
Patches
A fix has been implemented that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. See #1345
Workarounds
LDAP administrators can disallow unauthenticated bind requests by clients.
References
https://tools.ietf.org/html/rfc4513#section-5.1.2
https://pypi.org/project/alerta-server/8.1.0/
For more information
If you have any questions or comments about this advisory:
Impact
Users may be able to bypass LDAP authentication if they provide an empty password when Alerta server is configure to use LDAP as the authorization provider.
Only deployments where LDAP servers are configured to allow unauthenticated binds (eg. default on Active Directory) are affected.
Patches
A fix has been implemented that returns HTTP 401 Unauthorized response for any authentication attempts where the password field is empty. See #1345
Workarounds
LDAP administrators can disallow unauthenticated bind requests by clients.
References
https://tools.ietf.org/html/rfc4513#section-5.1.2
https://pypi.org/project/alerta-server/8.1.0/
For more information
If you have any questions or comments about this advisory: