# CVE-2023-32781: Command injection in n/a

> Authenticated users with write permissions can exploit the HL7 sensor debug option to execute arbitrary commands via the EXE/Script sensor.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6hrq-pjj8-qgcg

## What is CVE-2023-32781?

CVE-2023-32781 is a high-severity command injection vulnerability in n/a, published on 9 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A command injection vulnerability was identified in PRTG 23.2.84.1566 and earlier versions in the HL7 sensor where an authenticated user with write permissions could abuse the debug option to write new files that could potentially get executed by the EXE/Script sensor. The severity of this vulnerability is high and received a score of 7.2 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Paessler Prtg Network Monitor.

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

No fix has been published for CVE-2023-32781 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-32781 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32781 exists.

Public exploit code:

- PRTG CVE-2023-32781 Authenticated RCE (metasploit)

## Other vulnerabilities in n/a

- [CVE-2018-19410](https://insights.sbomify.com/CVE-2018-19410/): Paessler PRTG Network Monitor Local File Inclusion (critical 9.8, exploited in the wild)
- [CVE-2018-9276](https://insights.sbomify.com/CVE-2018-9276/): Paessler PRTG Network Monitor OS Command Injection (high 7.2, exploited in the wild)
- [CVE-2020-10374](https://insights.sbomify.com/CVE-2020-10374/): Command injection in n/a (critical 9.8)
- [CVE-2023-51630](https://insights.sbomify.com/CVE-2023-51630/): Paessler PRTG Network Monitor Cross-Site Scripting Authentication Bypass Vulnerability (high 8.8)
- [CVE-2023-31452](https://insights.sbomify.com/CVE-2023-31452/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32781 is a high-severity command injection vulnerability in n/a, published on 9 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32781 exists.

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

## Sources

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

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