dbcve.org
ZabbixApplication

CVE-2024-22116

HIGH · 7.2 CVSS v3.1 Published 2024-08-12
Fix available
A fix is available. Upgrade to after 6.4.15 or later.
See remediation →
78/100
Remediation priority · High
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 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.

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

A restricted administrator can execute arbitrary code through the Monitoring Hosts script execution functionality due to improper escaping of script parameters in the Ping script, allowing full infrastructure compromise.

MitigationImplement proper input sanitization and escaping for all script parameters in the Monitoring Hosts functionality, particularly for the Ping script, and apply any vendor-provided security patches.

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:>= 6.4.9, <= 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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify Zabbix installation and version
    Check the Zabbix version by logging into the web UI (footer displays version), running 'zabbix_server -V' on the server, or querying the Zabbix API endpoint /apiinfo/version. Compare against affected versions: 6.4.9 through 6.4.15, and version 7.0.0.
    Affected if The installed Zabbix version falls within 6.4.9-6.4.15 or equals 7.0.0
  2. Confirm restricted administrator access exists
    Verify that there are user accounts with "Admin" or "User" level permissions (not Super Admin) in Administration → Users. These are considered restricted administrators who should not have full infrastructure access.
    Affected if Restricted (non-Super Admin) user accounts exist in the Zabbix installation
  3. Verify Monitoring Hosts script execution is enabled
    Check if the script execution feature is enabled in Zabbix. This can be confirmed by navigating to Monitoring → Hosts in the web UI. If scripts can be executed from the host list view, the feature is active. Also verify in Administration → Scripts that script execution is permitted.
    Affected if Script execution from the Monitoring Hosts interface is accessible to restricted administrator accounts
  4. Confirm Ping script is configured and accessible
    Navigate to Administration → Scripts in the Zabbix web UI and verify that a script with "ping" or similar functionality exists and is assigned to the Monitoring Hosts host list. The vulnerability specifically affects the Ping script parameter handling.
    Affected if A Ping script is configured and available for execution from the Monitoring Hosts view

You are affected if running Zabbix version 6.4.9-6.4.15 or 7.0.0 AND a restricted administrator can execute scripts via Monitoring Hosts with the Ping script available.

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 proper input sanitization and escaping for all script parameters in the Monitoring Hosts functionality, particularly for the Ping script, and apply any vendor-provided security patches.

Recommended fix High confidence

Zabbix 6.4.16 or later / Zabbix 7.0.1 or later

  1. 1. Back up your current Zabbix configuration and database before upgrading
  2. 2. Download Zabbix 6.4.16 or later (for 6.4.x line) or Zabbix 7.0.1 or later (for 7.0.x line) from the official Zabbix repository at zabbix.com
  3. 3. Upgrade the Zabbix server component first, followed by the frontend (if applicable)
  4. 4. After upgrade, verify that the 'Ping' script and other custom scripts function correctly
  5. 5. Review user permissions to ensure the principle of least privilege is maintained
Caveat Always test upgrades in a staging environment first; review release notes for any configuration changes between versions

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

Fix this in Zabbix Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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