HertzBeat: Deserialization of Untrusted Data
CVE-2024-42362 is a high-severity deserialization of untrusted data vulnerability in HertzBeat from Apache, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected HertzBeat versions: < 1.6.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.33% chance of exploitation within 30 days, higher than 72% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update hertzbeat to 1.6.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | HertzBeat | < 1.6.0 | Not stated |
| Dromara | hertzbeat | before 1.6.0 | 1.6.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CNA (github.com) |
| CVSS 3.1 | 8.8 | High | NVD |
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Deserialization of Untrusted Data
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
How developers prevent this class of flaw
- If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
- When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
- Explicitly define a final object() to prevent deserialization.
More Deserialization of Untrusted Data vulnerabilities (CWE-502)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/apache/hertzbeat/commit/79f5408e345e8e89da97be05f43e3204a950ddfb
- github.com/apache/hertzbeat/commit/9dbbfb7812fc4440ba72bdee66799edd519d06bb
- github.com/apache/hertzbeat/pull/1611
- github.com/apache/hertzbeat/pull/1620
- github.com/apache/hertzbeat/pull/1620/files#diff-9c5fb3d1b7e3b0f54bc5c4182965c4fe1f9023d449017cece3005d3f90e8…
Technical write-ups (may include proof of concept)
- securitylab.github.com/advisories/GHSL-2023-254_GHSL-2023-256_HertzBeat/Exploit, Third Party Advisory
Other vulnerabilities in HertzBeat
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 8.8 High severity
Recent Deserialization of Untrusted Data vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 10.0 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.