Skip to content
Fencer Vulns
medium 6.8

CVE-2023-32727 json

Code execution vulnerability in icmpping

published 2023-12-18 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-36954

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits
0
none known

Summary

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.

Patch / fix

  • zabbix Debian 14, Debian 13 1:6.0.23+dfsg-1

debian advisories DEBIAN-CVE-2023-32727

  • zabbix openSUSE Tumbleweed 6.0.25-1.1
  • zabbix Package Hub 15 SP4, openSUSE Leap 15.4 4.0.50-bp154.2.9.1
  • zabbix Package Hub 15 SP5, openSUSE Leap 15.5 4.0.50-bp155.3.9.1

opensuse advisories openSUSE-SU-2024:13535-1openSUSE-SU-2023:0419-1openSUSE-SU-2023:0418-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-32727 updated cvss 6.8

zabbix: potential arbitrary code execution in icmpping() function

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
18 mo ago

Exploit prediction

0.87% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
NVD 3.1 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Zabbix Zabbix

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.