Authenticated code execution via unsafe YAML deserialization
Published Aug 20, 2024 · Updated Aug 21, 2024
Unsafe deserialization in Apache HertzBeat before 1.6.0 allows remote authenticated users to execute arbitrary code through monitor imports. YamlImExportServiceImpl.parseImport passes the uploaded YAML stream to SnakeYAML Yaml.load, which instantiates attacker-selected Java objects. Access requires an admin or user role; a crafted import can load a remote malicious JAR and execute commands in the server process.
Summary
What happened
Unsafe deserialization in Apache HertzBeat before 1.6.0 allows remote authenticated users to execute arbitrary code through monitor imports. YamlImExportServiceImpl.parseImport passes the uploaded YAML stream to SnakeYAML Yaml.load, which instantiates attacker-selected Java objects. Access requires an admin or user role; a crafted import can load a remote malicious JAR and execute commands in the server process.
The record
- CVE
- CVE-2024-42362
- Published
- Aug 20, 2024
- Updated
- Aug 21, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache HertzBeat
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 21, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.6.0
- Affected versionversion=< 1.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub Security Lab monitor-import YAML proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo