Security 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 59th percentile
Risk Priority 34 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

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, ranked in the top 41% 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

CVEs Like This One

CVE-2023-22348Same product: Checkmk Checkmk
CVE-2023-6735Same product: Checkmk Checkmk
CVE-2023-0284Same product: Checkmk Checkmk
CVE-2023-22288Same product: Checkmk Checkmk
CVE-2023-31211Same product: Checkmk Checkmk
CVE-2023-6740Same product: Checkmk Checkmk
CVE-2023-31209Same product: Checkmk Checkmk
CVE-2023-31208Same product: Checkmk Checkmk
CVE-2024-28830Same product: Checkmk Checkmk
CVE-2024-28831Same product: Checkmk Checkmk

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

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 Secure development life cycle partial match
blocks

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
blocks

A.8.26 only requires that security requirements (including resilience against attacks such as SQL injection) be identified and specified during development or acquisition; it does not itself enforce, implement, or configure any UI behavior that would stop a discrepancy between actual security state and what the UI reports to the user.

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

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

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

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-446, a class-level weakness. Rules are authored against its narrower children: CWE-449.

References