dbcve.org
ZabbixApplication

CVE-2023-32722

HIGH · 7.8 CVSS v3.1 Published 2023-10-12
Fix available
A fix is available. Upgrade to after 6.4.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
The zabbix/src/libs/zbxjson module is vulnerable to a buffer overflow when parsing JSON files via zbx_json_open.

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 buffer overflow vulnerability exists in Zabbix's zbxjson library module (zabbix/src/libs/zbxjson) when parsing JSON files through the zbx_json_open function. This memory corruption issue could allow an attacker to overwrite adjacent memory regions by supplying specially crafted JSON input, potentially leading to arbitrary code execution or denial of service.

MitigationUpdate Zabbix to the latest version containing the security patch for this vulnerability. If immediate patching is not feasible, restrict or validate JSON file inputs and limit exposure of the zbx_json_open function to untrusted sources.

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.0.0, <= 6.0.20>= 6.4.0, <= 6.4.5= 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 if Zabbix is installed
    Run 'zabbix_server --version' or 'zabbix_agentd --version' to identify the Zabbix components and version installed on the system.
    Affected if No output or Zabbix not found means the system is not affected by this specific vulnerability.
  2. Verify the installed version against affected ranges
    Compare the installed Zabbix version number to the affected ranges: 6.0.0 through 6.0.20, 6.4.0 through 6.4.5, or 7.0.0 exactly. If the version falls within any of these ranges, the system is potentially affected.
    Affected if The installed version is 6.0.0-6.0.20, 6.4.0-6.4.5, or 7.0.0.
  3. Identify JSON input sources processed by Zabbix
    Review Zabbix configuration files (typically zabbix_server.conf or zabbix_agentd.conf) and check for items, traps, or templates that process JSON data. Look for user parameters, external checks, or HTTP agent items that accept JSON input.
    Affected if Zabbix is configured to accept or process JSON data from external or user-defined sources.
  4. Assess exposure of zbx_json_open function
    Examine logs or network traffic for JSON-based communication such as Zabbix sender data, trapper items, or API calls that involve JSON parsing. Check if the Zabbix server or agent handles JSON from untrusted network sources.
    Affected if Zabbix processes JSON data from untrusted or external sources without additional validation.

A system is affected if Zabbix is installed with a version in the ranges 6.0.0-6.0.20, 6.4.0-6.4.5, or 7.0.0, and the system processes JSON input through the zbx_json_open function from any source.

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

Update Zabbix to the latest version containing the security patch for this vulnerability. If immediate patching is not feasible, restrict or validate JSON file inputs and limit exposure of the zbx_json_open function to untrusted sources.

Recommended fix Moderate confidence

Zabbix 6.0.21+, 6.4.6+, or 7.0.1+ (depending on your major version branch)

  1. 1. Identify the currently installed Zabbix version using 'zabbix_server --version' or checking the package manager.
  2. 2. For Zabbix 6.0.x installations: upgrade to version 6.0.21 or later.
  3. 3. For Zabbix 6.4.x installations: upgrade to version 6.4.6 or later.
  4. 4. For Zabbix 7.0.x installations: upgrade to version 7.0.1 or later.
  5. 5. After upgrading, restart the Zabbix server service using 'systemctl restart zabbix-server' or the appropriate service manager command.
  6. 6. Verify the upgrade was successful by checking the Zabbix server version again and ensuring normal operation.
Caveat Review Zabbix release notes for any breaking changes between your current version and the target upgrade version before proceeding

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-2023-32722 — 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-32722 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