CVE Vulnerabilities

CVE-2023-2020

Improper Handling of Insufficient Permissions or Privileges

Published: Apr 18, 2023 | Modified: Nov 21, 2024
CVSS 3.x
4.3
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

Insufficient permission checks in the REST API in Tribe29 Checkmk <= 2.1.0p27 and <= 2.2.0b4 (beta) allow unauthorized users to schedule downtimes for any host.

Weakness

The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.

Affected Software

Name Vendor Start Version End Version
Checkmk Checkmk 2.1.0 (including) 2.1.0 (including)
Checkmk Checkmk 2.1.0-b1 (including) 2.1.0-b1 (including)
Checkmk Checkmk 2.1.0-b2 (including) 2.1.0-b2 (including)
Checkmk Checkmk 2.1.0-b3 (including) 2.1.0-b3 (including)
Checkmk Checkmk 2.1.0-b4 (including) 2.1.0-b4 (including)
Checkmk Checkmk 2.1.0-b5 (including) 2.1.0-b5 (including)
Checkmk Checkmk 2.1.0-b6 (including) 2.1.0-b6 (including)
Checkmk Checkmk 2.1.0-b7 (including) 2.1.0-b7 (including)
Checkmk Checkmk 2.1.0-b8 (including) 2.1.0-b8 (including)
Checkmk Checkmk 2.1.0-b9 (including) 2.1.0-b9 (including)
Checkmk Checkmk 2.1.0-p1 (including) 2.1.0-p1 (including)
Checkmk Checkmk 2.1.0-p10 (including) 2.1.0-p10 (including)
Checkmk Checkmk 2.1.0-p11 (including) 2.1.0-p11 (including)
Checkmk Checkmk 2.1.0-p12 (including) 2.1.0-p12 (including)
Checkmk Checkmk 2.1.0-p13 (including) 2.1.0-p13 (including)
Checkmk Checkmk 2.1.0-p14 (including) 2.1.0-p14 (including)
Checkmk Checkmk 2.1.0-p15 (including) 2.1.0-p15 (including)
Checkmk Checkmk 2.1.0-p16 (including) 2.1.0-p16 (including)
Checkmk Checkmk 2.1.0-p17 (including) 2.1.0-p17 (including)
Checkmk Checkmk 2.1.0-p18 (including) 2.1.0-p18 (including)
Checkmk Checkmk 2.1.0-p2 (including) 2.1.0-p2 (including)
Checkmk Checkmk 2.1.0-p20 (including) 2.1.0-p20 (including)
Checkmk Checkmk 2.1.0-p21 (including) 2.1.0-p21 (including)
Checkmk Checkmk 2.1.0-p22 (including) 2.1.0-p22 (including)
Checkmk Checkmk 2.1.0-p23 (including) 2.1.0-p23 (including)
Checkmk Checkmk 2.1.0-p24 (including) 2.1.0-p24 (including)
Checkmk Checkmk 2.1.0-p25 (including) 2.1.0-p25 (including)
Checkmk Checkmk 2.1.0-p26 (including) 2.1.0-p26 (including)
Checkmk Checkmk 2.1.0-p27 (including) 2.1.0-p27 (including)
Checkmk Checkmk 2.1.0-p3 (including) 2.1.0-p3 (including)
Checkmk Checkmk 2.1.0-p4 (including) 2.1.0-p4 (including)
Checkmk Checkmk 2.1.0-p5 (including) 2.1.0-p5 (including)
Checkmk Checkmk 2.1.0-p6 (including) 2.1.0-p6 (including)
Checkmk Checkmk 2.1.0-p7 (including) 2.1.0-p7 (including)
Checkmk Checkmk 2.1.0-p8 (including) 2.1.0-p8 (including)
Checkmk Checkmk 2.1.0-p9 (including) 2.1.0-p9 (including)
Checkmk Checkmk 2.2.0-b1 (including) 2.2.0-b1 (including)
Checkmk Checkmk 2.2.0-b2 (including) 2.2.0-b2 (including)
Checkmk Checkmk 2.2.0-b3 (including) 2.2.0-b3 (including)
Checkmk Checkmk 2.2.0-b4 (including) 2.2.0-b4 (including)
Checkmk Checkmk 2.2.0-i1 (including) 2.2.0-i1 (including)
Check-mk Ubuntu bionic *
Check-mk Ubuntu trusty *
Check-mk Ubuntu xenial *

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References