CVE-2023-6156
Checkmk 2.0.0 … 2.2.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-6156 is a high-severity Improper Neutralization of Delimiters (CWE-140) vulnerability in Checkmk Checkmk. Its CVSS base score is 7.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Protocol or Service Impersonation (T1001.003); ranked in the top 42% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-58406
Vulnerability Data
Improper neutralization of livestatus command delimiters in the availability timeline in Checkmk <= 2.0.0p39, < 2.1.0p37, and < 2.2.0p15 allows arbitrary livestatus command execution for authorized users.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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 proper delimiter neutralization during input handling and output encoding.
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.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, testing (scans/penetration), and developer training that reach improper neutralization of delimiters, but leaves a bounded remainder (e.g. inconsistent application across outsourced development, incomplete coverage of all languages or legacy code, and non-mandatory enforcement of the full set of practices).
Application security requirements include input validation and output encoding that mitigate delimiter mishandling.
Secure coding explicitly requires proper neutralization of delimiters to prevent injection and parsing flaws.
Security testing in development and acceptance can detect delimiter-related weaknesses before deployment.