# CVE-2023-29450: Unauthorized limited filesystem access from preprocessing

> Attackers can exploit JavaScript preprocessing to gain unauthorized read-only access to the server filesystem, exposing sensitive data.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-29450, GHSA-hfrc-jq43-4m6c, SUSE-SU-2023:3029-1, UBUNTU-CVE-2023-29450

## What is CVE-2023-29450?

CVE-2023-29450 is a high-severity path traversal vulnerability in Zabbix Zabbix, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-29450?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zabbix` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.0.12-4.24.1 |
| `zabbix` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.0.12-4.24.1 |

Products: Zabbix Zabbix.

## How do I fix CVE-2023-29450?

Apply the vendor's patch.

## Is CVE-2023-29450 being exploited?

There is no known exploitation of CVE-2023-29450 in the wild and no public exploit code.

## Other vulnerabilities in Zabbix Zabbix

- [CVE-2022-23131](https://insights.sbomify.com/CVE-2022-23131/): Zabbix Frontend Authentication Bypass (critical 9.1, exploited in the wild)
- [CVE-2007-0640](https://insights.sbomify.com/CVE-2007-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-42327](https://insights.sbomify.com/CVE-2024-42327/): SQL injection in user.get API (critical 9.9)
- [CVE-2024-22116](https://insights.sbomify.com/CVE-2024-22116/): Remote code execution within ping script (critical 9.9)
- [CVE-2013-3738](https://insights.sbomify.com/CVE-2013-3738/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29450 and fix it if it is affected.

What it is: CVE-2023-29450 is a high-severity path traversal vulnerability in Zabbix Zabbix, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29450 in the wild and no public exploit code.

Affected product: Zabbix Zabbix. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-29450/ (Markdown: https://insights.sbomify.com/CVE-2023-29450/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-29450
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-29450
- OSV: https://osv.dev/vulnerability/CVE-2023-29450

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-29450/
Summaries are generated and may contain mistakes; the official description above is the record.