In Zabbix from 4.0.x before 4.0.28rc1, 5.0.0alpha1 before 5.0.10rc1, 5.2.x before 5.2.6rc1, and 5.4.0alpha1 before 5.4.0beta2, the CControllerAuthenticationUpdate controller lacks a CSRF protection mechanism. The code inside this controller calls diableSIDValidation inside the init() method. An attacker doesn't have to know Zabbix user login credentials, but has to know the correct Zabbix URL and contact information of an existing user with sufficient privileges.

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3390 advisory.

  - Zabbix through 4.4.0alpha1 allows User Enumeration. With login requests, it is possible to enumerate     application usernames based on the variability of server responses (e.g., the Login name or password is     incorrect and No permissions for system access messages, or just blocking for a number of seconds).
    This affects both api_jsonrpc.php and index.php. (CVE-2019-15132)

  - Zabbix before 3.0.32rc1, 4.x before 4.0.22rc1, 4.1.x through 4.4.x before 4.4.10rc1, and 5.x before     5.0.2rc1 allows stored XSS in the URL Widget. (CVE-2020-15803)

  - In Zabbix from 4.0.x before 4.0.28rc1, 5.0.0alpha1 before 5.0.10rc1, 5.2.x before 5.2.6rc1, and     5.4.0alpha1 before 5.4.0beta2, the CControllerAuthenticationUpdate controller lacks a CSRF protection     mechanism. The code inside this controller calls diableSIDValidation inside the init() method. An attacker     doesn't have to know Zabbix user login credentials, but has to know the correct Zabbix URL and contact     information of an existing user with sufficient privileges. (CVE-2021-27927)

  - An authenticated user can create a link with reflected XSS payload for actions' pages, and send it to     other users. Malicious code has access to all the same objects as the rest of the web page and can make     arbitrary modifications to the contents of the page being displayed to a victim. This attack can be     implemented with the help of social engineering and expiration of a number of factors - an attacker should     have authorized access to the Zabbix Frontend and allowed network connection between a malicious server     and victim's computer, understand attacked infrastructure, be recognized by the victim as a trustee and     use trusted communication channel. (CVE-2022-24349)

  - An authenticated user can create a link with reflected Javascript code inside it for services' page and     send it to other users. The payload can be executed only with a known CSRF token value of the victim,     which is changed periodically and is difficult to predict. Malicious code has access to all the same     objects as the rest of the web page and can make arbitrary modifications to the contents of the page being     displayed to a victim during social engineering attacks. (CVE-2022-24917)

  - An authenticated user can create a link with reflected Javascript code inside it for graphs' page and send     it to other users. The payload can be executed only with a known CSRF token value of the victim, which is     changed periodically and is difficult to predict. Malicious code has access to all the same objects as the     rest of the web page and can make arbitrary modifications to the contents of the page being displayed to a     victim during social engineering attacks. (CVE-2022-24919)

  - An authenticated user can create a link with reflected Javascript code inside it for the graphs page and     send it to other users. The payload can be executed only with a known CSRF token value of the victim,     which is changed periodically and is difficult to predict. (CVE-2022-35230)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SUSE15 host has packages installed that are affected by multiple vulnerabilities as referenced in the openSUSE-SU-2022:0036-1 advisory.

  - Zabbix before 3.0.32rc1, 4.x before 4.0.22rc1, 4.1.x through 4.4.x before 4.4.10rc1, and 5.x before     5.0.2rc1 allows stored XSS in the URL Widget. (CVE-2020-15803)

  - In Zabbix from 4.0.x before 4.0.28rc1, 5.0.0alpha1 before 5.0.10rc1, 5.2.x before 5.2.6rc1, and     5.4.0alpha1 before 5.4.0beta2, the CControllerAuthenticationUpdate controller lacks a CSRF protection     mechanism. The code inside this controller calls diableSIDValidation inside the init() method. An attacker     doesn't have to know Zabbix user login credentials, but has to know the correct Zabbix URL and contact     information of an existing user with sufficient privileges. (CVE-2021-27927)

  - After the initial setup process, some steps of setup.php file are reachable not only by super-     administrators, but by unauthenticated users as well. Malicious actor can pass step checks and potentially     change the configuration of Zabbix Frontend. (CVE-2022-23134)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

This update for zabbix fixes the following issues :

CVE-2021-27927: Fixed an improper CSRF protection mechanism (bsc#1183014).

CVE-2013-7484: Fixed an issue where passwords in the users table were unsalted (bsc#1158321).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Severity
174179	Debian DLA-3390-1 : zabbix - LTS security update	Nessus	Debian Local Security Checks	high
158130	openSUSE 15 Security Update : zabbix (openSUSE-SU-2022:0036-1)	Nessus	SuSE Local Security Checks	high
148252	SUSE SLES12 Security Update : zabbix (SUSE-SU-2021:0990-1)	Nessus	SuSE Local Security Checks	high

Detections

Analytics

CVE-2021-27927

high

Tenable Plugins

high

high

high