CVE-2023-22318
Tribe29 Checkmk Appliance Firmware ≤ 1.6.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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-22318 is a high-severity Unrestricted Externally Accessible Lock (CWE-412) vulnerability in Tribe29 Checkmk Appliance Firmware. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique LSASS Memory (T1003.001); ranked at the 44th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-26481
Vulnerability Data
Denial of service in Webconf in Tribe29 Checkmk Appliance before 1.6.5.
- 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.
Vulnerability identification processes can discover externally controllable locks before deployment.
Enforcing least-privilege authorization policies directly prevents external actors from acquiring or influencing locks.
Logical access controls and segmentation stop unintended external influence over synchronization primitives.
Hardened configuration baselines can disable or restrict external lock exposure by default.
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.
Privileged access rights limit who can create or manipulate locks, reducing external influence.
Secure development lifecycle practices can prevent introducing externally controllable locks during design.
A.8.26 only requires that security requirements (including resilience against attacks such as injections) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent exploitation of an externally influenced lock.
A.8.27 mandates establishing and applying secure-by-design principles (defense-in-depth, least privilege, fail securely, distrust external input, zero-trust verification) during architecture and engineering; CWE-412 is a concrete implementation flaw (lock check that can be externally overridden) that can still be introduced and exploited even when those principles are followed, as the control does not itself enforce or verify the specific lock-isolation logic.
Secure coding guidelines can enforce internal-only lock control during implementation.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-667, a class-level weakness, and none of its children carries one either.