Filtered by vendor Zabbix
Subscribe
Total
88 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2024-36460 | 1 Zabbix | 1 Zabbix | 2024-12-10 | N/A | 8.1 HIGH |
The front-end audit log allows viewing of unprotected plaintext passwords, where the passwords are displayed in plain text. | |||||
CVE-2024-22114 | 1 Zabbix | 1 Zabbix | 2024-12-04 | N/A | 4.3 MEDIUM |
User with no permission to any of the Hosts can access and view host count & other statistics through System Information Widget in Global View Dashboard. | |||||
CVE-2024-22116 | 1 Zabbix | 1 Zabbix | 2024-12-04 | N/A | 9.9 CRITICAL |
An administrator with restricted permissions can exploit the script execution functionality within the Monitoring Hosts section. The lack of default escaping for script parameters enabled this user ability to execute arbitrary code via the Ping script, thereby compromising infrastructure. | |||||
CVE-2024-22119 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 5.5 MEDIUM |
The cause of vulnerability is improper validation of form input field “Name” on Graph page in Items section. | |||||
CVE-2023-32728 | 1 Zabbix | 1 Zabbix-agent2 | 2024-11-21 | N/A | 4.6 MEDIUM |
The Zabbix Agent 2 item key smart.disk.get does not sanitize its parameters before passing them to a shell command resulting possible vulnerability for remote code execution. | |||||
CVE-2023-32727 | 1 Zabbix | 1 Zabbix Server | 2024-11-21 | N/A | 6.8 MEDIUM |
An attacker who has the privilege to configure Zabbix items can use function icmpping() with additional malicious command inside it to execute arbitrary code on the current Zabbix server. | |||||
CVE-2023-32726 | 1 Zabbix | 1 Zabbix-agent | 2024-11-21 | N/A | 3.9 LOW |
The vulnerability is caused by improper check for check if RDLENGTH does not overflow the buffer in response from DNS server. | |||||
CVE-2023-32725 | 1 Zabbix | 2 Frontend, Zabbix Server | 2024-11-21 | N/A | 9.6 CRITICAL |
The website configured in the URL widget will receive a session cookie when testing or executing scheduled reports. The received session cookie can then be used to access the frontend as the particular user. | |||||
CVE-2023-32724 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 9.1 CRITICAL |
Memory pointer is in a property of the Ducktape object. This leads to multiple vulnerabilities related to direct memory access and manipulation. | |||||
CVE-2023-32723 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 8.5 HIGH |
Request to LDAP is sent before user permissions are checked. | |||||
CVE-2023-32722 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 9.6 CRITICAL |
The zabbix/src/libs/zbxjson module is vulnerable to a buffer overflow when parsing JSON files via zbx_json_open. | |||||
CVE-2023-32721 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 7.6 HIGH |
A stored XSS has been found in the Zabbix web application in the Maps element if a URL field is set with spaces before URL. | |||||
CVE-2023-30958 | 1 Zabbix | 1 Frontend | 2024-11-21 | N/A | 4.7 MEDIUM |
A security defect was identified in Foundry Frontend that enabled users to potentially conduct DOM XSS attacks if Foundry's CSP were to be bypassed. This defect was resolved with the release of Foundry Frontend 6.225.0. | |||||
CVE-2023-29458 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 5.9 MEDIUM |
Duktape is an 3rd-party embeddable JavaScript engine, with a focus on portability and compact footprint. When adding too many values in valstack JavaScript will crash. This issue occurs due to bug in Duktape 2.6 which is an 3rd-party solution that we use. | |||||
CVE-2023-29457 | 1 Zabbix | 1 Frontend | 2024-11-21 | N/A | 6.3 MEDIUM |
Reflected XSS attacks, occur when a malicious script is reflected off a web application to the victim's browser. The script can be activated through Action form fields, which can be sent as request to a website with a vulnerability that enables execution of malicious scripts. | |||||
CVE-2023-29455 | 1 Zabbix | 1 Frontend | 2024-11-21 | N/A | 5.4 MEDIUM |
Reflected XSS attacks, also known as non-persistent attacks, occur when a malicious script is reflected off a web application to the victim's browser. The script is activated through a link, which sends a request to a website with a vulnerability that enables execution of malicious scripts. | |||||
CVE-2023-29453 | 1 Zabbix | 1 Zabbix-agent2 | 2024-11-21 | N/A | 9.8 CRITICAL |
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g., "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template. Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution. | |||||
CVE-2023-29452 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 5.5 MEDIUM |
Currently, geomap configuration (Administration -> General -> Geographical maps) allows using HTML in the field “Attribution text” when selected “Other” Tile provider. | |||||
CVE-2023-29451 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 4.7 MEDIUM |
Specially crafted string can cause a buffer overrun in the JSON parser library leading to a crash of the Zabbix Server or a Zabbix Proxy. | |||||
CVE-2023-29450 | 1 Zabbix | 1 Zabbix | 2024-11-21 | N/A | 8.5 HIGH |
JavaScript pre-processing can be used by the attacker to gain access to the file system (read-only access on behalf of user "zabbix") on the Zabbix Server or Zabbix Proxy, potentially leading to unauthorized access to sensitive data. |