# CVE-2024-42327: SQL injection in user.get API

> A non-admin user with API access can exploit SQL injection in the user.get API to read or modify database contents.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/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:** 27 Nov 2024
- **Updated:** 4 Dec 2024
- **Also known as:** DEBIAN-CVE-2024-42327, GHSA-gx59-7g62-6xhg, UBUNTU-CVE-2024-42327

## What is CVE-2024-42327?

CVE-2024-42327 is a critical SQL injection vulnerability in Zabbix Zabbix, published on 27 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A non-admin user account on the Zabbix frontend with the default User role, or with any other role that gives API access can exploit this vulnerability. An SQLi exists in the CUser class in the addRelatedObjects function, this function is being called from the CUser.get function which is available for every user who has API access.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-42327?

It affects 1 product.


Products: Zabbix Zabbix.

## How do I fix CVE-2024-42327?

Apply the vendor's patch.

## Is CVE-2024-42327 being exploited?

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

Public exploit code:

- Zabbix CVE-2024-42327 PoC (github_poc): https://github.com/BridgerAlderson/Zabbix-CVE-2024-42327-SQL-Injection-RCE
- cve-2024-42327 ZBX-25623 (github_poc): https://github.com/aramosf/cve-2024-42327
- PoC for CVE-2024-42327 / ZBX-25623 (github_poc): https://github.com/compr00t/CVE-2024-42327
- Proof of concept for CVE-2024-42327: Zabbix privilege escalation to RCE (github_poc): https://github.com/godylockz/CVE-2024-42327
- https://github.com/depers-rus/CVE-2024-42327 (github_poc): https://github.com/depers-rus/CVE-2024-42327
- POC for CVE-2024-42327, an authenticated SQL Injection in Zabbix through the user.get API Method (github_poc): https://github.com/watchdog1337/CVE-2024-42327_Zabbix_SQLI

## 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-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)
- [CVE-2013-5743](https://insights.sbomify.com/CVE-2013-5743/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42327 and fix it if it is affected.

What it is: CVE-2024-42327 is a critical SQL injection vulnerability in Zabbix Zabbix, published on 27 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42327 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-2024-42327/ (Markdown: https://insights.sbomify.com/CVE-2024-42327/index.md)
```

## Sources

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

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