dbcve.org
ZabbixApplication

CVE-2024-22121

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to after 6.4.15 or later.
See remediation →
63/100
Remediation priority · Elevated
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
A non-admin user can change or remove important features within the Zabbix Agent application, thus impacting the integrity and availability of the application.

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 authorization vulnerability in Zabbix Agent where non-admin users can modify or remove critical application features, compromising system integrity and availability. The flaw allows unprivileged users to alter agent configurations or functionality that should be restricted to administrators.

MitigationImplement role-based access controls (RBAC) to ensure non-admin users cannot modify agent configurations or features; restrict elevated permissions to admin accounts only.

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.42>= 6.0.0, <= 6.0.30>= 6.4.0, <= 6.4.15= 7.0.0

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

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

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. Identify Zabbix Agent installation and version
    Run 'zabbix_agentd --version' or check package manager for Zabbix Agent version (e.g., 'dpkg -l zabbix-agent' or 'rpm -qi zabbix-agent')
    Affected if Installed version falls within 5.0.0-5.0.42, 6.0.0-6.0.30, 6.4.0-6.4.15, or is exactly 7.0.0
  2. Check Zabbix user role assignments
    Access Zabbix web frontend or query the users table in the Zabbix database to review role assignments for non-admin users
    Affected if Any non-administrator user account is assigned a role with permissions to modify agent configurations or critical features
  3. Inspect agent configuration file access controls
    Check file permissions on Zabbix Agent configuration files (e.g., zabbix_agentd.conf) using 'ls -la' - verify only root or zabbix user has write access
    Affected if Configuration files are writable by non-privileged users or groups outside the Zabbix service account
  4. Verify authorization controls for API/frontend actions
    Review Zabbix user group permissions and role definitions in the Zabbix database, specifically checking if 'write' or 'execute' permissions exist for 'scripts', 'actions', or 'conf' object types for non-admin users
    Affected if Non-admin users have been granted write permissions to scripts, actions, or configuration objects that control agent behavior

A user is affected if Zabbix Agent version is within the affected ranges AND non-administrator accounts have elevated permissions to modify agent configurations or critical system features.

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 a release after 6.4.15
Interim mitigation

Implement role-based access controls (RBAC) to ensure non-admin users cannot modify agent configurations or features; restrict elevated permissions to admin accounts only.

Recommended fix Moderate confidence

Zabbix 5.0.43+/6.0.31+/6.4.16+/7.0.1+ (depending on your major version branch)

  1. 1. Identify your current Zabbix version by checking the Zabbix Agent and Server package/version
  2. 2. For Zabbix 5.0.x: Upgrade to version 5.0.43 or later
  3. 3. For Zabbix 6.0.x: Upgrade to version 6.0.31 or later
  4. 4. For Zabbix 6.4.x: Upgrade to version 6.4.16 or later
  5. 5. For Zabbix 7.0.0: Upgrade to version 7.0.1 or later
  6. 6. After upgrading, verify that non-admin users can no longer modify or remove critical Zabbix Agent features
  7. 7. Test that the Zabbix Agent continues to function correctly with the upgraded version
Caveat Review Zabbix release notes for your version branch to check for any configuration or feature changes between versions

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22121 — 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-22121 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