Authenticated Livestatus command injection via unescaped POST data
Published Apr 10, 2025 · Updated Apr 10, 2025
Command injection in Checkmk before 2.2.0p39, 2.3.0p25, and 2.1.0p51 allows remote authenticated users to execute Livestatus commands. A REST API endpoint fails to escape POST data before incorporating it into a Livestatus command, so delimiters introduce additional arbitrary commands. Exploitation requires event update and acknowledgment permission, an assigned contact group, and a matching-group or unknown-host event.
Summary
What happened
Command injection in Checkmk before 2.2.0p39, 2.3.0p25, and 2.1.0p51 allows remote authenticated users to execute Livestatus commands. A REST API endpoint fails to escape POST data before incorporating it into a Livestatus command, so delimiters introduce additional arbitrary commands. Exploitation requires event update and acknowledgment permission, an assigned contact group, and a matching-group or unknown-host event.
The record
- CVE
- CVE-2024-38865
- Published
- Apr 10, 2025
- Updated
- Apr 10, 2025
- Vendor
- Checkmk GmbH
- Product
- Checkmk
- Classifications
- CWE-140, CAPEC-15, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 10, 2025CVE publishedPublication date reported by the CVE source.
- Apr 10, 2025Record 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=2.1.0 <=2.1.0p50
- Affected versionversion=2.2.0 <2.2.0p39
- Affected versionversion=2.3.0 <2.3.0p25
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
No public exploit references are available in this record.
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