Unauthorized limited filesystem access from preprocessing

published 2023-07-13 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-33019

cvss: 8.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 69%
public exploits: 0; none known

JavaScript pre-processing can be used by the attacker to gain access to the file system (read-only access on behalf of user "zabbix") on the Zabbix Server or Zabbix Proxy, potentially leading to unauthorized access to sensitive data.

Patch / fix

distros 2

debian suse

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

debian advisories DEBIAN-CVE-2023-29450

zabbix SLES for SAP 12 SP5, SLES 12 SP5 4.0.12-4.24.1

suse advisories SUSE-SU-2023:3029-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-29450 updated 2025-11-21 cvss 3.3

zabbix: Unautorized file system access in JS preprocessing

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: 2 y ago (2024-11-06)

Exploit prediction

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

CVSS scores

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

Affected products

Zabbix Zabbix

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-552 Files or Directories Accessible to External Parties

References

Sources

CVE List CVE-2023-29450
NVD CVE-2023-29450

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.

Summary