CVE-2022-23131: Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAML
In the case of instances where the SAML SSO authentication is enabled (non-default), session data can be modified by a malicious actor, because a user login stored in the session was not verified. Malicious unauthenticated actor may exploit this issue to escalate privileges and gain admin access to Zabbix Frontend. To perform the attack, SAML authentication is required to be enabled and the actor has to know the username of Zabbix user (or use the guest account, which is disabled by default).
Other sources
Unsafe client-side session storage leading to authentication bypass/instance takeover via Zabbix Frontend with configured SAML.
— CISA
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Disable SAML SSO authentication in the Zabbix Frontend (turn off SAML-based authentication) until a security update is applied.
Zabbix Frontend SAML SSO authentication = disabled - Configuration
Ensure the guest account is disabled in Zabbix Frontend to prevent use of that account as an entry point for the vulnerability.
Zabbix Frontend guest account = disabled
Event History
Frequently Asked Questions
What is the severity of CVE-2022-23131?
The severity of CVE-2022-23131 is critical.
How can a malicious actor exploit CVE-2022-23131?
A malicious actor can exploit CVE-2022-23131 to escalate privileges and gain admin access.
Which software versions are affected by CVE-2022-23131?
Versions 5.4.0 to 5.4.8 of Zabbix Frontend and version 6.0.0-alpha1 of Zabbix are affected by CVE-2022-23131.
Is there a patch available for CVE-2022-23131?
Yes, a patch is available for CVE-2022-23131.
Where can I find more information about CVE-2022-23131?
You can find more information about CVE-2022-23131 at the Zabbix support website: https://support.zabbix.com/browse/ZBX-20350.