98 results (0.008 seconds)

CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0

02 Apr 2025 — Zabbix server is vulnerable to a DoS vulnerability due to uncontrolled resource exhaustion. An attacker can send specially crafted requests to the server, which will cause the server to allocate an excessive amount of memory and perform CPU-intensive decompression operations, ultimately leading to a service crash. • https://support.zabbix.com/browse/ZBX-26253 • CWE-770: Allocation of Resources Without Limits or Throttling •

CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0

02 Apr 2025 — The endpoint /zabbix.php?action=export.valuemaps suffers from a Cross-Site Scripting vulnerability via the backurl parameter. This is caused by the reflection of user-supplied data without appropriate HTML escaping or output encoding. As a result, a JavaScript payload may be injected into the above endpoint causing it to be executed within the context of the victim's browser. • https://support.zabbix.com/browse/ZBX-26254 • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •

CVSS: 5.3EPSS: 0%CPEs: 4EXPL: 0

02 Apr 2025 — Zabbix API user.get returns all users that share common group with the calling user. This includes media and other information, such as login attempts, etc. • https://support.zabbix.com/browse/ZBX-26258 • CWE-359: Exposure of Private Personal Information to an Unauthorized Actor •

CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0

02 Apr 2025 — Execution time for an unsuccessful login differs when using a non-existing username compared to using an existing one. • https://support.zabbix.com/browse/ZBX-26255 • CWE-208: Observable Timing Discrepancy •

CVSS: 8.8EPSS: 0%CPEs: 2EXPL: 0

02 Apr 2025 — A low privilege (regular) Zabbix user with API access can use SQL injection vulnerability in include/classes/api/CApiService.php to execute arbitrary SQL commands via the groupBy parameter. • https://support.zabbix.com/browse/ZBX-26257 • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') •

CVSS: 9.0EPSS: 0%CPEs: 2EXPL: 0

28 Nov 2024 — A bug in the code allows an attacker to sign a forged zbx_session cookie, which then allows them to sign in with admin permissions. Un error en el código permite a un atacante firmar una cookie zbx_session falsificada, que luego le permite iniciar sesión con permisos de administrador. • https://support.zabbix.com/browse/ZBX-25635 • CWE-290: Authentication Bypass by Spoofing •

CVSS: 3.3EPSS: 0%CPEs: 2EXPL: 0

27 Nov 2024 — When exporting media types, the password is exported in the YAML in plain text. This appears to be a best practices type issue and may have no actual impact. The user would need to have permissions to access the media types and therefore would be expected to have access to these passwords. • https://support.zabbix.com/browse/ZBX-25630 • CWE-256: Plaintext Storage of a Password •

CVSS: 3.3EPSS: 0%CPEs: 3EXPL: 0

27 Nov 2024 — The researcher is showing that it is possible to leak a small amount of Zabbix Server memory using an out of bounds read in src/libs/zbxmedia/email.c El investigador está demostrando que es posible filtrar una pequeña cantidad de memoria del servidor Zabbix mediante una lectura fuera de los límites en src/libs/zbxmedia/email.c • https://support.zabbix.com/browse/ZBX-25629 • CWE-126: Buffer Over-read •

CVSS: 3.7EPSS: 0%CPEs: 3EXPL: 0

27 Nov 2024 — The researcher is showing that due to the way the SNMP trap log is parsed, an attacker can craft an SNMP trap with additional lines of information and have forged data show in the Zabbix UI. This attack requires SNMP auth to be off and/or the attacker to know the community/auth details. The attack requires an SNMP item to be configured as text on the target host. El investigador demuestra que, debido a la forma en que se analiza el registro de trampas SNMP, un atacante puede manipular una trampa SNMP con lí... • https://support.zabbix.com/browse/ZBX-25628 •

CVSS: 3.3EPSS: 0%CPEs: 1EXPL: 0

27 Nov 2024 — In the src/libs/zbxembed/browser.c file, the es_browser_ctor method retrieves a heap pointer from the Duktape JavaScript engine. This heap pointer is subsequently utilized by the browser_push_error method in the src/libs/zbxembed/browser_error.c file. A use-after-free bug can occur at this stage if the wd->browser heap pointer is freed by garbage collection. En el archivo src/libs/zbxembed/browser.c, el método es_browser_ctor recupera un puntero de montón del motor JavaScript de Duktape. Este puntero de mon... • https://support.zabbix.com/browse/ZBX-25627 • CWE-416: Use After Free •