# CVE-2023-51653: Hertzbeat JMX JNDI RCE

> Attackers can achieve remote code execution in Hertzbeat via JNDI injection in the JMX monitoring interface.

- **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:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2024
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-gcmp-vf6v-59gg

## What is CVE-2023-51653?

CVE-2023-51653 is a critical code injection vulnerability in dromara hertzbeat, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hertzbeat is a real-time monitoring system. In the implementation of `JmxCollectImpl.java`, `JMXConnectorFactory.connect` is vulnerable to JNDI injection. The corresponding interface is `/api/monitor/detect`. If there is a URL field, the address will be used by default. When the URL is `service:jmx:rmi:///jndi/rmi://xxxxxxx:1099/localHikari`, it can be exploited to cause remote code execution. Version 1.4.1 contains a fix for this issue.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Apache Hertzbeat.

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

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

## Is CVE-2023-51653 being exploited?

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

## Other vulnerabilities in dromara hertzbeat

- [CVE-2023-51388](https://insights.sbomify.com/CVE-2023-51388/): HertzBeat AviatorScript Inject RCE (critical 9.8)
- [CVE-2023-51389](https://insights.sbomify.com/CVE-2023-51389/): HertzBeat SnakeYAML Deser RCE (critical 9.8)
- [CVE-2026-24343](https://insights.sbomify.com/CVE-2026-24343/): Apache HertzBeat: Uncontrolled Resource Consumption via Crafted XPath Expressions (high 8.8)
- [CVE-2025-24404](https://insights.sbomify.com/CVE-2025-24404/): Apache HertzBeat (incubating): RCE by parse http sitemap xml response (high 8.8)
- [CVE-2025-48208](https://insights.sbomify.com/CVE-2025-48208/): Apache HertzBeat (incubating): Jmx JNDI injection vulnerability (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51653 is a critical code injection vulnerability in dromara hertzbeat, published on 22 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-51653 in the wild and no public exploit code.

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

## Sources

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

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