dbcve.org
ZabbixApplication

CVE-2024-36467

HIGH · 8.8 CVSS v3.1 Published 2024-11-27
Fix available
A fix is available. Upgrade to 5.0.43 / 6.0.33 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an improper authorization vulnerability in Zabbix's user.update API endpoint. An authenticated user with basic User role can call the user.update API to add themselves to privileged groups (like Zabbix Administrators), effectively escalating their privileges beyond what their role should permit. The endpoint fails to properly validate authorization when modifying group memberships.

MitigationImplement proper authorization checks on the user.update API endpoint to verify the requesting user has permission to modify group memberships, particularly for adding users to privileged groups. Consider restricting API access for non-admin users or implementing group-level permission controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZabbixApplication
Affected:>= 5.0.0, < 5.0.43>= 6.0.0, < 6.0.33>= 6.4.0, < 6.4.18>= 7.0.0, < 7.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Zabbix version
    Locate the Zabbix server version by reviewing the Zabbix web interface footer, running 'zabbix_server -V' on the server host, or querying the API endpoint 'apiinfo.version'. Compare this version against the affected ranges: 5.0.0-5.0.42, 6.0.0-6.0.32, 6.4.0-6.4.17, and 7.0.0-7.0.1.
    Affected if The installed version falls within any of the listed vulnerable version ranges
  2. Verify Zabbix API is enabled
    Check the Zabbix server configuration file (zabbix.conf.php in the frontend directory) for the setting 'API_ENABLED' or equivalent, or attempt a simple API call to the /api/jsonrpc.php endpoint to confirm it accepts requests.
    Affected if The Zabbix API is accessible and accepts requests
  3. Confirm basic user role can access user.update
    Log in as a non-administrator user with only basic User role. Using an API client (such as curl), attempt to call the user.update method with a request that includes adding the user to a privileged group (usrgrpid for Zabbix Administrators or Super Admins). Inspect the API response for success versus authorization error.
    Affected if The API returns success and allows a basic User role to modify their own group memberships to privileged groups
  4. Inspect user group permission configuration
    In the Zabbix web interface, navigate to Users > User Groups. Review the group settings for 'Zabbix Administrators' and 'Super admin' groups. Check whether the group's permissions allow API access or whether there are restrictions on which user roles can modify group memberships via the API.
    Affected if Basic users have permissions that permit API-based modification of their group assignments

A user is affected if their Zabbix installation runs a version within the vulnerable range, the API is enabled, and basic User role accounts can successfully call user.update to add themselves to privileged groups.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.0.43 / 6.0.33 / 6.4.18 or later
Fixed in 5.0.436.0.336.4.18
Interim mitigation

Implement proper authorization checks on the user.update API endpoint to verify the requesting user has permission to modify group memberships, particularly for adding users to privileged groups. Consider restricting API access for non-admin users or implementing group-level permission controls.

Recommended fix High confidence

Upgrade to Zabbix 5.0.43, 6.0.33, 6.4.18, or 7.0.2 (or later) matching your current major version

  1. 1. Backup your current Zabbix database and configuration files before proceeding with the upgrade.
  2. 2. Identify your current Zabbix version from the Zabbix web interface (Reports > System information) or using the zabbix_server -V command.
  3. 3. Download the appropriate fixed version from official Zabbix download sources (zabbix.com/download) matching your current major version.
  4. 4. Stop the Zabbix server service: sudo systemctl stop zabbix-server
  5. 5. Upgrade Zabbix server packages using your system's package manager (e.g., yum, apt, or dnf) with the downloaded packages.
  6. 6. Review and update configuration files if required (usually located in /etc/zabbix/).
  7. 7. Start the Zabbix server service: sudo systemctl start zabbix-server
  8. 8. Verify the upgrade was successful by checking the Zabbix web interface Reports > System information shows the new version.
Caveat Standard upgrade considerations apply - review Zabbix release notes for your version for any breaking changes between your current and target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zabbix Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36467 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data