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).
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Zabbix | Zabbix | 5.4.0 (including) | 5.4.8 (including) |
| Zabbix | Zabbix | 6.0.0-alpha1 (including) | 6.0.0-alpha1 (including) |
| Zabbix | Ubuntu | bionic | * |
| Zabbix | Ubuntu | hirsute | * |
| Zabbix | Ubuntu | impish | * |
| Zabbix | Ubuntu | kinetic | * |
| Zabbix | Ubuntu | lunar | * |
| Zabbix | Ubuntu | trusty | * |
| Zabbix | Ubuntu | upstream | * |
| Zabbix | Ubuntu | xenial | * |