CVE-2024-1742
Checkmk ≤ 2.0.0
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:NSummary
CVE-2024-1742 is a low-severity Invocation of Process Using Visible Sensitive Information (CWE-214) vulnerability in Checkmk Checkmk. Its CVSS base score is 3.8 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-4 (Information in Shared System Resources) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17469
Vulnerability Data
Invocation of the sqlplus command with sensitive information in the command line in the mk_oracle Checkmk agent plugin before Checkmk 2.3.0b4 (beta), 2.2.0p24, 2.1.0p41 and 2.0.0 (EOL) allows the extraction of this information from the process list.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.5
Mitigating Controls (NIST 800-53 r5) AI
Prevents unintended transfer of sensitive command-line arguments or environment variables through shared OS resources visible to other processes.
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.
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.
Restricting privileged utility programs reduces the chance that sensitive invocation data is exposed to other processes.
Privileged access rights reduce exposure of sensitive command-line arguments to unauthorized observers.
Secure coding practices can prevent passing sensitive data via command-line arguments or environment variables.
Information access restriction limits visibility of process arguments and environment variables to authorized users only.
Separation of environments limits the blast radius if sensitive invocation data is exposed.