# CVE-2023-32728: Code injection in zabbix_agent2 smart.disk.get caused by smartctl plugin

> Attackers can execute arbitrary code on Zabbix Agent 2 hosts by exploiting unsanitized parameters in the smart.disk.get item key.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Dec 2023
- **Updated:** 27 Nov 2024
- **Also known as:** DEBIAN-CVE-2023-32728, GHSA-c26q-v9gv-jx6m, UBUNTU-CVE-2023-32728

## What is CVE-2023-32728?

CVE-2023-32728 is a medium-severity command injection vulnerability in Zabbix, published on 18 Dec 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Zabbix Agent 2 item key smart.disk.get does not sanitize its parameters before passing them to a shell command resulting possible vulnerability for remote code execution.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Zabbix Zabbix-Agent2.

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

Apply the vendor's patch.

## Is CVE-2023-32728 being exploited?

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

## Other vulnerabilities in Zabbix

- [CVE-2023-29453](https://insights.sbomify.com/CVE-2023-29453/): Agent 2 package are built with Go version affected by CVE-2023-24538 (critical 9.8)
- [CVE-2022-22704](https://insights.sbomify.com/CVE-2022-22704/): Privilege escalation in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32728 is a medium-severity command injection vulnerability in Zabbix, published on 18 Dec 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-32728 in the wild and no public exploit code.

Affected product: 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-32728/ (Markdown: https://insights.sbomify.com/CVE-2023-32728/index.md)
```

## Sources

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

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