Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2023-37679: Remote command execution in NextGen Mirth Connect 4.3.0

Published Aug 3, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS99.4%100th percentile
CISA KEVNoNot listed
In the wildReported558 exploitation records in Mallory
Vendor
Nextgen
IdentifiersCVE-2023-37679CWE-94

CVE-2023-37679 is a remote command execution vulnerability in NextGen Mirth Connect 4.3.0 that allows attackers to execute arbitrary commands on the hosting server. Nation-state and ransomware actors have exploited this vulnerability as a network entry point. The vulnerable function, underlying weakness, and precise exploitation mechanism are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary command execution on the Mirth Connect hosting server and can provide an initial foothold in the surrounding network. Exploitation has been associated with ransomware operations, including Storm-1175 campaigns involving Medusa ransomware. The execution privilege level and specific confidentiality or availability effects of the vulnerability are not established.

Mitigation

If you can’t patch tonight, do this now.

Reduce exposure of Mirth Connect through managed firewalls and appropriate VPN restrictions. Apply MFA to remote-access services and continuously monitor the external attack surface. These are defense-in-depth measures; their effectiveness against the specific exploit is not established.

Remediation

Patch, then assume compromise.

Upgrade Mirth Connect to version 4.4.0 or later, which fully addresses the vulnerability. Additionally, discontinue the use of JRE 8.0, as future releases will not support it. Ensure that all instances are running the latest supported version and that the management interface is not exposed to the Internet.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
mirth_connect_cve_2023_43208.rbThis repository contains a single Metasploit module targeting Mirth Connect (NextGen) for two deserialization vulnerabilities: CVE-2023-37679 and CVE-2023-43208. The exploit leverages crafted XML payloads sent via POST requests to the /api/users endpoint, exploiting insecure deserialization to achieve remote code execution (RCE) on both Linux and Windows platforms. The module includes logic to fingerprint the target version using the /api/server/version endpoint and selects the appropriate gadget chain based on the detected version. The exploit is weaponized, supporting arbitrary command execution as a Metasploit payload, and does not require authentication. The code is well-structured, with clear separation of version detection, exploit logic, and payload delivery. The default configuration targets port 8443 over SSL, but these can be customized. The module is suitable for both proof-of-concept and operational exploitation.Disclosed Oct 25, 2023 · Framework: metasploit · ruby · networkWeaponizedCVE-2023-43208Repository contains a single Python exploit (exploit.py) plus documentation (README.md) targeting CVE-2023-43208: a pre-auth remote code execution vulnerability in NextGen Healthcare Mirth Connect versions < 4.4.1. The exploit sends a crafted XStream XML payload to the unauthenticated POST /api/users endpoint. The payload is a deserialization gadget chain that bypasses the prior denylist-based fix for CVE-2023-37679 by using org.apache.commons.lang3.event.EventUtils$EventBindingInvocationHandler (dynamic proxy handler) together with Apache Commons Collections4 transformers (ChainedTransformer/ConstantTransformer/InvokerTransformer) to invoke java.lang.Runtime.getRuntime().exec(command). Key capabilities implemented via argparse subcommands: - check: fingerprints the target (uses /api/server/version) and assesses likely vulnerability. - exec: performs blind command execution (no command output expected). - shell: triggers a reverse shell back to attacker-supplied --lhost/--lport and includes listener handling (socket/select/threading indicated by imports and CLI options). - scan: multi-target scanning from a file with configurable thread count and optional output of vulnerable hosts. Notable operational details: uses Python requests with TLS warnings disabled (suggesting self-signed certs common on :8443), sets headers including Content-Type: application/xml and X-Requested-With: OpenAPI, and builds/escapes XML to embed arbitrary commands safely into the serialized gadget chain.kyakei · Disclosed Feb 22, 2026 · python · network (pre-auth HTTP(S) POST to Mirth Connect REST API endpoint triggering XStream XML deserialization)OperationalCVE-2023-43208Repository contains a standalone Python exploit for NextGen Mirth Connect targeting CVE-2023-43208 (and referencing CVE-2023-37679). The main file (CVE-2023-43208.py) builds an XML payload that leverages a Java gadget chain (Apache Commons Collections4 + Commons Lang3 EventUtils invocation handler) to invoke java.lang.Runtime.exec() on the server. It sends the payload via an unauthenticated HTTP POST to the Mirth Connect API endpoint /api/users with headers Content-Type: application/xml and X-Requested-With: OpenAPI, with TLS verification disabled. Capabilities: - Arbitrary command execution (one-shot) on the target host; optional Windows command wrapping using cmd.exe /c. - Reverse shell mode: if -lh/-lp are provided, it auto-generates a bash /dev/tcp reverse shell command to connect back to the attacker. - Includes a simple built-in TCP listener (binds 0.0.0.0:<port>) to accept a single incoming connection and print received data. Repository structure: - CVE-2023-43208.py: exploit implementation, CLI parsing, payload generation, HTTP delivery, optional listener. - README.md: high-level vulnerability description and affected versions (claims up to 4.4.0; fixed in 4.4.1). - use.txt: usage examples for command execution and reverse shell (notes using netcat externally; script also has its own listener).D3m0nicw0lf · Disclosed Feb 25, 2026 · python · markdown · network (HTTP pre-auth deserialization leading to RCE)OperationalCVE-2023-37679The repository contains seven files: two Python programs, a Dockerfile, Docker Compose configuration, bilingual documentation, an MIT license, and .gitignore. poc/poc.py is a standalone exploit client; mock/mock_mirth.py is an intentionally vulnerable HTTP simulator. The Docker configuration runs the simulator as an unprivileged user, drops all capabilities, enables no-new-privileges, and publishes its port only on host loopback. No exploit framework, external command-and-control endpoint, or bundled malware is present. The original repository URL, git reference, and archive size were not supplied; size_bytes is therefore an unknown-value placeholder of 0. Listed file sizes total 17,170 bytes, which is not an archive-size measurement. The client constructs a Java XStream gadget document and POSTs it to /api/users with X-Requested-With: OpenAPI, Content-Type: application/xml, and User-Agent: curl/8.5.0. It supports configurable commands, targets, ports, marker names, and HTTPS; HTTPS certificate verification is disabled. The default payload touches a web-accessible marker file, followed by a GET verification request. Commands with ordinary arguments are supported despite documentation claiming commands must contain no spaces; automatic shell parsing, pipelines, and redirection are not provided. Command text is inserted into XML without escaping, so XML-special characters can break the payload. The simulator does not run Java, XStream, or the actual gadget chain. It uses a regular expression to extract the final matching iArgs/string value and executes cmd.split() through subprocess.run(), with a six-second timeout. Consequently, successful laboratory execution demonstrates only the simulated pre-authentication command sink, not compatibility with a real Mirth installation. It returns a Tomcat-like HTTP 500 page containing java.lang.reflect.InvocationTargetException even when execution fails, so HTTP 500 is not reliable proof of compromise. The client does not verify command success in custom-command mode; marker verification can also accept a previously existing file. The repository identifies CVE-2023-37679 and Mirth Connect 4.3.0 as its primary target, and discusses CVE-2023-43208 with version 4.4.0 as a related bypass. These vulnerability mappings and version claims are documentation assertions, not independently validated by the supplied mock. Additional limitations include string-prefix-based local-address classification, which can misclassify public addresses beginning with 172.2, and private targets inheriting laboratory connection defaults. Fetch/chmod/run staging is mentioned in documentation but is not implemented as an automated chain.krevetkqqq · Disclosed Oct 30, 2026 · python · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NextgenMirth Connectapplication
FAQ

Frequently asked questions

Is CVE-2023-37679 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2023-37679?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2023-37679, the earliest disclosed Oct 25, 2023.
Is there a patch for CVE-2023-37679?
Upgrade Mirth Connect to version 4.4.0 or later, which fully addresses the vulnerability. Additionally, discontinue the use of JRE 8.0, as future releases will not support it.
What products are affected by CVE-2023-37679?
Nextgen Mirth Connect.
How severe is CVE-2023-37679?
CVE-2023-37679 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 99.4% (100th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.