CVE-2024-42362 GHSL-2023-255: HertzBeat Authenticated (user role) RCE via unsafe deserialization in /api/monitors/import
Authenticated users can execute arbitrary code via unsafe deserialization in the monitor import API, requiring an upgrade to secure the monitoring system.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-42362?
CVE-2024-42362 is a high-severity unsafe deserialization vulnerability in Apache HertzBeat, published on 20 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Hertzbeat is an open source, real-time monitoring system. Hertzbeat has an authenticated (user role) RCE via unsafe deserialization in /api/monitors/import. This vulnerability is fixed in 1.6.0.
Weakness: CWE-502
Which versions are affected by CVE-2024-42362?
It affects 1 product.
Products include Apache Hertzbeat.
How do I fix CVE-2024-42362?
No fix has been published for CVE-2024-42362 yet. Limit exposure of the affected software until one is available.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2024-42362 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42362 exists.
Other vulnerabilities in Apache HertzBeat
- CVE-2023-51388 HertzBeat AviatorScript Inject RCE
- CVE-2023-51389 HertzBeat SnakeYAML Deser RCE
- CVE-2023-51653 Hertzbeat JMX JNDI RCE
- CVE-2026-24343 Apache HertzBeat: Uncontrolled Resource Consumption via Crafted XPath Expressions
- CVE-2025-24404 Apache HertzBeat (incubating): RCE by parse http sitemap xml response