Cyber Resilience

CVE-2023-1768

Checkmk 1.6.0 … 2.2.0

Published
04 April 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 3.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0091 57th percentile
Risk Priority 34 floored blend · peak EPSS

Summary

CVE-2023-1768 is a low-severity UI Discrepancy for Security Feature (CWE-446) vulnerability in Checkmk Checkmk. Its CVSS base score is 3.7 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Subvert Trust Controls (T1553); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

Inappropriate error handling in Tribe29 Checkmk <= 2.1.0p25, <= 2.0.0p34, <= 2.2.0b3 (beta), and all versions of Checkmk 1.6.0 causes the symmetric encryption of agent data to fail silently and transmit the data in plaintext in certain configurations.

CWE(s)
CWE-446NVD-CWE-Other

Related Threats

MITRE ATT&CK Enterprise Techniques

T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
attack.mitre.org →
T1557 Adversary-in-the-Middle Credential Access
Adversaries may attempt to position themselves between two or more networked devices using an adversary-in-the-middle (AiTM) technique to support follow-on behaviors such as [Network Sniffing](https://attack.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-31209Same product: Checkmk Checkmk
CVE-2023-22348Same product: Checkmk Checkmk
CVE-2023-0284Same product: Checkmk Checkmk
CVE-2023-6735Same product: Checkmk Checkmk
CVE-2023-31208Same product: Checkmk Checkmk
CVE-2023-6740Same product: Checkmk Checkmk
CVE-2023-22288Same product: Checkmk Checkmk
CVE-2023-31211Same product: Checkmk Checkmk
CVE-2024-6572Same product: Checkmk Checkmk
CVE-2025-52983Shared CWE-446

Affected Assets

checkmk
checkmk
1.6.0, 2.0.0, 2.1.0, 2.2.0
tribe29
checkmk
1.6.0b10, 1.6.0b11, 1.6.0p10, 1.6.0p11, 1.6.0p12

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 1 OS baseline
Validate
Prove the fix (OWASP ASVS)

—

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require accurate UI representation of security configuration state.

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.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect UI discrepancies before release, providing strong mitigation for this weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires UI security features to be correctly implemented and verified, directly preventing misleading security-state feedback.

A.8.26 Application security requirements partial match
prevents

Application security requirements should specify correct UI behavior for security controls, reducing the chance of misleading user feedback.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles can guide UI design but do not specifically address misleading security-state indicators.

A.8.28 Secure coding partial match
prevents

Secure coding practices help avoid implementation bugs that cause UI discrepancies, though the control is not focused on UI correctness.

A.8.5 Secure authentication none match
none

Secure authentication control may be undermined by UI discrepancies, but eliminating the weakness does not implement the authentication mechanism itself.

References