During Zabbix installation from RPM, DAC_OVERRIDE SELinux capability is in use to access PID files in [/var/run/zabbix] folder. In this case, Zabbix Proxy or Server processes can bypass file read, write and execute permissions check on the file system level
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Zabbix | Zabbix | 4.0.0 (including) | 4.0.36 (including) |
Zabbix | Zabbix | 5.0.0 (including) | 5.0.18 (including) |
Zabbix | Zabbix | 5.4.0 (including) | 5.4.8 (including) |
Zabbix | Zabbix | 6.0.0-alpha1 (including) | 6.0.0-alpha1 (including) |
Zabbix | Zabbix | 6.0.0-alpha2 (including) | 6.0.0-alpha2 (including) |
Zabbix | Zabbix | 6.0.0-alpha3 (including) | 6.0.0-alpha3 (including) |
Zabbix | Zabbix | 6.0.0-alpha4 (including) | 6.0.0-alpha4 (including) |
Zabbix | Zabbix | 6.0.0-alpha5 (including) | 6.0.0-alpha5 (including) |
Zabbix | Zabbix | 6.0.0-alpha6 (including) | 6.0.0-alpha6 (including) |
Zabbix | Zabbix | 6.0.0-alpha7 (including) | 6.0.0-alpha7 (including) |
Zabbix | Ubuntu | bionic | * |
Zabbix | Ubuntu | esm-apps/focal | * |
Zabbix | Ubuntu | esm-apps/jammy | * |
Zabbix | Ubuntu | focal | * |
Zabbix | Ubuntu | hirsute | * |
Zabbix | Ubuntu | impish | * |
Zabbix | Ubuntu | jammy | * |
Zabbix | Ubuntu | kinetic | * |
Zabbix | Ubuntu | lunar | * |
Zabbix | Ubuntu | trusty | * |
Zabbix | Ubuntu | upstream | * |
Zabbix | Ubuntu | xenial | * |
Access control involves the use of several protection mechanisms such as:
When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses: