dbcve.org
Zabbix ServerApplication · Zabbix

CVE-2023-32727

HIGH · 7.2 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to after 6.4.7 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 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.

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 · high confidence

This is an authenticated command injection vulnerability in Zabbix Server where an attacker with privileges to configure monitoring items can inject malicious commands through the icmpping() function, achieving arbitrary code execution on the Zabbix server itself.

MitigationRestrict the ability to create/configure items to only trusted administrators, and apply the vendor patch to sanitize input in the icmpping() function to prevent command injection.

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
Zabbix ServerApplication
Affected:>= 4.0.0, <= 4.0.49>= 5.0.0, <= 5.0.38>= 6.0.0, <= 6.0.22>= 6.4.0, <= 6.4.7= 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. Check Zabbix Server version
    Run `zabbix_server --version` or check the About section in the Zabbix web interface under Administration > Reports > System information
    Affected if The installed version falls within 4.0.0-4.0.49, 5.0.0-5.0.38, 6.0.0-6.0.22, 6.4.0-6.4.7, or 7.0.0
  2. Verify user privileges for item configuration
    Navigate to Administration > Users > User or Role settings and review permissions under the Items or Monitoring > Items section
    Affected if Any user or role has permissions to create or edit monitoring items (particularly ICMP ping items)
  3. Identify configured ICMP ping items
    Check the Zabbix database for items with key containing 'icmpping' using query like: SELECT itemid, key_, name FROM items WHERE key_ LIKE '%icmpping%'
    Affected if Any items with icmpping, icmppingloss, or icmppingsec keys exist in the configuration

The environment is affected if the Zabbix Server version is within the vulnerable range AND untrusted users have privileges to configure ICMP ping monitoring items.

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.7
Interim mitigation

Restrict the ability to create/configure items to only trusted administrators, and apply the vendor patch to sanitize input in the icmpping() function to prevent command injection.

Recommended fix Moderate confidence

Zabbix 4.0.50+, 5.0.39+, 6.0.23+, 6.4.8+, or latest 6.4/7.0 LTS

  1. 1. Back up the current Zabbix configuration and database before proceeding with any upgrade.
  2. 2. Review the Zabbix upgrade documentation for your current major version to understand the upgrade path.
  3. 3. Upgrade from Zabbix 4.0.x to at least version 4.0.50 or migrate to a newer supported LTS version (5.0.x, 6.0.x, or 6.4.x).
  4. 4. If upgrading to 5.0.x, install version 5.0.39 or later.
  5. 5. If upgrading to 6.0.x, install version 6.0.23 or later.
  6. 6. If upgrading to 6.4.x, install version 6.4.8 or later.
  7. 7. Alternatively, upgrade directly to the latest Zabbix 6.4 LTS or 7.0 release which contains the fix.
  8. 8. After upgrade, verify the icmpping() function no longer allows arbitrary command execution.
Caveat Upgrading across major versions (e.g., 4.0 to 6.0) may require database migration and template/configuration updates; review breaking changes in Zabbix upgrade notes

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

Fix this in Zabbix Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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