# CVE-2023-43208: NextGen Healthcare Mirth Connect Deserialization of Untrusted Data

> Unauthenticated attackers can execute arbitrary code on NextGen Healthcare Mirth Connect servers due to incomplete patching of a previous vulnerability.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 20 May 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Oct 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-pj5c-qr29-6746

## What is CVE-2023-43208?

CVE-2023-43208 is a critical command injection vulnerability in n/a, published on 26 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NextGen Healthcare Mirth Connect before version 4.4.1 is vulnerable to unauthenticated remote code execution. Note that this vulnerability is caused by the incomplete patch of CVE-2023-37679.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Nextgen Mirth Connect.

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

No fix has been published for CVE-2023-43208 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Jun 2024.

## Is CVE-2023-43208 being exploited?

Yes. Attackers have exploited CVE-2023-43208 in the wild since at least 20 May 2024, including in ransomware campaigns.

Public exploit code:

- https://github.com/jakabakos/CVE-2023-43208-mirth-connect-rce-poc (github_poc): https://github.com/jakabakos/CVE-2023-43208-mirth-connect-rce-poc
- PoC for CVE-2023-43208 RCE exploitation. (github_poc): https://github.com/predyy/CVE-2023-43208
- CVE-2023-43208: Mirth Connect Pre-Auth RCE PoC (github_poc): https://github.com/kyakei/CVE-2023-43208
- A proof-of-concept exploit for CVE-2023-43208, a remote code execution vulnerability in Mirth Connect before version 4.4.1. (github_poc): https://github.com/MKIRAHMET/PoC-2023-43208
- Use java.net.InetAddress for detection (github_poc): https://github.com/Avento/CVE-2023-43208_Detection_PoC
- Python implementation of CVE-2023-43208 Mirth Connect RCE (Unauth XStream) (github_poc): https://github.com/azrvs/Mirth-Connect-CVE-2023-43208

## Other vulnerabilities in n/a

- [CVE-2023-37679](https://insights.sbomify.com/CVE-2023-37679/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-43208 is a critical command injection vulnerability in n/a, published on 26 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-43208 in the wild since at least 20 May 2024, including in ransomware campaigns.

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

## Sources

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

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