zabbix - Debian Package Tracker

general

source: zabbix (main)
version: 1:7.0.6+dfsg-1
maintainer: Dmitry Smirnov (DMD)
uploaders: Christoph Haas [DMD]
arch: all any
std-ver: 4.6.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1:4.0.4+dfsg-1
o-o-sec: 1:4.0.4+dfsg-1+deb10u5
oldstable: 1:5.0.8+dfsg-1
old-sec: 1:5.0.45+dfsg-1+deb11u1
old-bpo: 1:6.0.14+dfsg-1~bpo11+1
stable: 1:6.0.14+dfsg-1
stable-bpo: 1:7.0.5+dfsg-1~bpo12+1
unstable: 1:7.0.6+dfsg-1

versioned links

1:4.0.4+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:4.0.4+dfsg-1+deb10u5: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:5.0.8+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:5.0.45+dfsg-1+deb11u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:6.0.14+dfsg-1~bpo11+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:6.0.14+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:7.0.5+dfsg-1~bpo12+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1:7.0.6+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

zabbix-agent (2 bugs: 0, 1, 1, 0)
zabbix-agent2 (2 bugs: 0, 2, 0, 0)
zabbix-frontend-php (3 bugs: 0, 2, 1, 0)
zabbix-java-gateway
zabbix-proxy-mysql (1 bugs: 0, 0, 1, 0)
zabbix-proxy-pgsql
zabbix-proxy-sqlite3
zabbix-sender
zabbix-server-mysql (3 bugs: 0, 1, 2, 0)
zabbix-server-pgsql
zabbix-web-service

action needed

A new upstream version is available: 7.0.8 high

A new upstream version 7.0.8 is available, you should consider packaging it.

Created: 2024-12-22 Last update: 2025-01-17 19:00

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2024-36464: 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.
CVE-2024-42328: When the webdriver for the Browser object downloads data from a HTTP server, the data pointer is set to NULL and is allocated only in curl_write_cb when receiving data. If the server's response is an empty document, then wd->data in the code below will remain NULL and an attempt to read from it will result in a crash.

Created: 2024-11-28 Last update: 2024-12-31 18:03

34 security issues in bookworm high

There are 34 open security issues in bookworm.

23 important issues:

CVE-2023-32724: Memory pointer is in a property of the Ducktape object. This leads to multiple vulnerabilities related to direct memory access and manipulation.
CVE-2023-32725: 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-32726: The vulnerability is caused by improper check for check if RDLENGTH does not overflow the buffer in response from DNS server.
CVE-2023-32727: 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-32728: 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-2024-22114: 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: 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-22117: When a URL is added to the map element, it is recorded in the database with sequential IDs. Upon adding a new URL, the system retrieves the last sysmapelementurlid value and increments it by one. However, an issue arises when a user manually changes the sysmapelementurlid value by adding sysmapelementurlid + 1. This action prevents others from adding URLs to the map element.
CVE-2024-22119: The cause of vulnerability is improper validation of form input field “Name” on Graph page in Items section.
CVE-2024-22120: Zabbix server can perform command execution for configured scripts. After command is executed, audit entry is added to "Audit Log". Due to "clientip" field is not sanitized, it is possible to injection SQL into "clientip" and exploit time based blind SQL injection.
CVE-2024-22122: Zabbix allows to configure SMS notifications. AT command injection occurs on "Zabbix Server" because there is no validation of "Number" field on Web nor on Zabbix server side. Attacker can run test of SMS providing specially crafted phone number and execute additional AT commands on modem.
CVE-2024-22123: Setting SMS media allows to set GSM modem file. Later this file is used as Linux device. But due everything is a file for Linux, it is possible to set another file, e.g. log file and zabbix_server will try to communicate with it as modem. As a result, log file will be broken with AT commands and small part for log file content will be leaked to UI.
CVE-2024-36460: The front-end audit log allows viewing of unprotected plaintext passwords, where the passwords are displayed in plain text.
CVE-2024-36461: Within Zabbix, users have the ability to directly modify memory pointers in the JavaScript engine.
CVE-2024-36463: The implementation of atob in "Zabbix JS" allows to create a string with arbitrary content and use it to access internal properties of objects.
CVE-2024-36464: 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.
CVE-2024-36466: 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.
CVE-2024-36467: An authenticated user with API access (e.g.: user with default User role), more specifically a user with access to the user.update API endpoint is enough to be able to add themselves to any group (e.g.: Zabbix Administrators), except to groups that are disabled or having restricted GUI access.
CVE-2024-42327: A non-admin user account on the Zabbix frontend with the default User role, or with any other role that gives API access can exploit this vulnerability. An SQLi exists in the CUser class in the addRelatedObjects function, this function is being called from the CUser.get function which is available for every user who has API access.
CVE-2024-42330: The HttpRequest object allows to get the HTTP headers from the server's response after sending the request. The problem is that the returned strings are created directly from the data returned by the server and are not correctly encoded for JavaScript. This allows to create internal strings that can be used to access hidden properties of objects.
CVE-2024-42331: 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.
CVE-2024-42332: 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.
CVE-2024-42333: 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

11 issues left for the package maintainer to handle:

CVE-2023-29449: (needs triaging) JavaScript preprocessing, webhooks and global scripts can cause uncontrolled CPU, memory, and disk I/O utilization. Preprocessing/webhook/global script configuration and testing are only available to Administrative roles (Admin and Superadmin). Administrative privileges should be typically granted to users who need to perform tasks that require more control over the system. The security risk is limited because not all users have this level of access.
CVE-2023-29450: (needs triaging) 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.
CVE-2023-29451: (needs triaging) 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-29452: (needs triaging) Currently, geomap configuration (Administration -> General -> Geographical maps) allows using HTML in the field “Attribution text” when selected “Other” Tile provider.
CVE-2023-29454: (needs triaging) Stored or persistent cross-site scripting (XSS) is a type of XSS where the attacker first sends the payload to the web application, then the application saves the payload (e.g., in a database or server-side text files), and finally, the application unintentionally executes the payload for every victim visiting its web pages.
CVE-2023-29455: (needs triaging) 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-29456: (needs triaging) URL validation scheme receives input from a user and then parses it to identify its various components. The validation scheme can ensure that all URL components comply with internet standards.
CVE-2023-29457: (needs triaging) 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-29458: (needs triaging) 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-32721: (needs triaging) 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-32722: (needs triaging) The zabbix/src/libs/zbxjson module is vulnerable to a buffer overflow when parsing JSON files via zbx_json_open.

You can find information about how to handle these issues in the security team's documentation.

Created: 2023-07-14 Last update: 2024-12-31 18:03

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2024-36464: 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.
CVE-2024-42328: When the webdriver for the Browser object downloads data from a HTTP server, the data pointer is set to NULL and is allocated only in curl_write_cb when receiving data. If the server's response is an empty document, then wd->data in the code below will remain NULL and an attempt to read from it will result in a crash.

Created: 2024-11-28 Last update: 2024-12-15 17:03

The package has not entered testing even though the delay is over normal

The package has not entered testing even though the 5-day delay is over. Check why.

Created: 2024-12-31 Last update: 2025-01-17 21:02

2 bugs tagged patch in the BTS normal

The BTS contains patches fixing 2 bugs, consider including or untagging them.

Created: 2025-01-06 Last update: 2025-01-17 21:01

Depends on packages which need a new maintainer normal

The packages that zabbix depends on which need a new maintainer are:

dh-linktree (#980413)
- Build-Depends: dh-linktree

Created: 2019-11-22 Last update: 2025-01-17 20:30

version in VCS is newer than in repository, is it time to upload? normal

vcswatch reports that this package seems to have a new changelog entry (version 1:7.0.6+dfsg-2, distribution UNRELEASED) and new commits in its VCS. You should consider whether it's time to make an upload.

Here are the relevant commit messages:

commit 931ff45b3baa8191e64e9d291f4247c0daa66ac9
Author: Tobias Frost <tobi@debian.org>
Date:   Sun Dec 15 17:06:29 2024 +0100

    More CVE annotations for past uploads.

commit 781781fc470f5d664c8d5e72de7c3b5d84cca104
Author: Tobias Frost <tobi@debian.org>
Date:   Sun Dec 15 15:33:22 2024 +0100

    Annotate past changelog entries with the CVE's they fix.

https://salsa.debian.org/api/v4/projects/debian%2Fzabbix/pipelines?scope=finished&per_page=1 API request failed: 403 Forbidden at /srv/qa.debian.org/data/vcswatch/vcswatch line 431.

Created: 2024-12-15 Last update: 2025-01-13 21:30

lintian reports 27 warnings normal

Lintian reports 27 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2024-11-24 Last update: 2024-11-24 16:31

debian/patches: 1 patch to forward upstream low

Among the 12 debian patches available in version 1:7.0.6+dfsg-1 of the package, we noticed the following issues:

1 patch where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2024-09-05 Last update: 2024-11-24 15:01

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.0 instead of 4.6.2).

Created: 2024-04-07 Last update: 2024-11-24 11:04

testing migrations

This package is part of the ongoing testing transition known as auto-openldap. Please avoid uploads unrelated to this transition, they would likely delay it and require supplementary work from the release managers. On the other hand, if your package has problems preventing it to migrate to testing, please fix them as soon as possible. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
This package will soon be part of the auto-libxml2 transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
- Migrates after: openldap
- Migration status for zabbix (- to 1:7.0.6+dfsg-1): BLOCKED: Rejected/violates migration policy/introduces a regression
- Issues preventing migration:
- ∙ ∙ Updating zabbix would introduce bugs in testing: #1090029, #1090030
- ∙ ∙ Depends: zabbix openldap
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/z/zabbix.html
- ∙ ∙ New but not reproducible on amd64 - info ♻
- ∙ ∙ New but not reproducible on arm64 - info ♻
- ∙ ∙ New but not reproducible on armhf - info ♻
- ∙ ∙ New but not reproducible on i386 - info ♻
- ∙ ∙ 55 days old (needed 5 days)
- Not considered

news

[rss feed]

[2025-01-01] zabbix REMOVED from testing (Debian testing watch)
[2024-12-07] Accepted zabbix 1:5.0.45+dfsg-1+deb11u1 (source) into oldstable-security (Tobias Frost)
[2024-11-29] zabbix 1:7.0.6+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-11-24] Accepted zabbix 1:7.0.6+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2024-11-06] Accepted zabbix 1:7.0.5+dfsg-1~bpo12+1 (source) into stable-backports (Dmitry Smirnov)
[2024-11-06] zabbix 1:7.0.5+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-11-01] Accepted zabbix 1:7.0.5+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2024-10-03] Accepted zabbix 1:5.0.44+dfsg-1+deb11u1 (source) into oldstable-security (Tobias Frost)
[2024-09-10] zabbix 1:7.0.3+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-09-05] Accepted zabbix 1:7.0.3+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2024-09-05] Accepted zabbix 1:7.0.2+dfsg-1~bpo12+1 (source) into stable-backports (Dmitry Smirnov)
[2024-08-06] zabbix 1:7.0.2+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-08-01] Accepted zabbix 1:7.0.2+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2024-08-01] Accepted zabbix 1:7.0.1+dfsg-1~bpo12+1 (source) into stable-backports (Dmitry Smirnov)
[2024-08-01] zabbix 1:7.0.1+dfsg-1 MIGRATED to testing (Debian testing watch)
[2024-07-27] Accepted zabbix 1:7.0.1+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2024-06-25] Accepted zabbix 1:7.0.0+dfsg-2~bpo12+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Dmitry Smirnov)
[2024-06-13] zabbix 1:7.0.0+dfsg-2 MIGRATED to testing (Debian testing watch)
[2024-06-07] Accepted zabbix 1:7.0.0+dfsg-2 (source) into unstable (Dmitry Smirnov)
[2024-06-06] Accepted zabbix 1:7.0.0+dfsg-1 (source amd64 all) into unstable (Debian FTP Masters) (signed by: Dmitry Smirnov)
[2024-04-28] Accepted zabbix 1:4.0.4+dfsg-1+deb10u5 (source) into oldoldstable (Adrian Bunk)
[2024-04-26] Accepted zabbix 1:6.0.29+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2024-03-27] zabbix REMOVED from testing (Debian testing watch)
[2024-03-27] zabbix REMOVED from testing (Debian testing watch)
[2024-01-24] Accepted zabbix 1:4.0.4+dfsg-1+deb10u4 (source) into oldoldstable (Tobias Frost)
[2024-01-05] zabbix 1:6.0.25+dfsg-1 MIGRATED to testing (Debian testing watch)
[2023-12-31] Accepted zabbix 1:6.0.25+dfsg-1 (source) into unstable (Dmitry Smirnov)
[2023-12-09] zabbix 1:6.0.24+dfsg-1 MIGRATED to testing (Debian testing watch)
[2023-12-07] Accepted zabbix 1:6.0.23+dfsg-1~bpo12+1 (source amd64 all) into stable-backports (Debian FTP Masters) (signed by: Dmitry Smirnov)
[2023-12-04] Accepted zabbix 1:6.0.24+dfsg-1 (source) into unstable (Dmitry Smirnov)

bugs [bug history graph]

all: 14
RC: 2
I&N: 6
M&W: 6
F&P: 0
patch: 2

links

homepage
lintian (0, 27)
buildd: logs, cross
popcon
browse source code
edit tags
other distros
security tracker
l10n (-, 53)
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1:7.0.6+dfsg-1
74 bugs (1 patch)