CVE-2022-48318: Insecure access control mechanisms for RestAPI documentation

Published Feb 20, 2023
·
Updated

No authorisation controls in the RestAPI documentation for Tribe29's Checkmk <= 2.1.0p13 and Checkmk <= 2.0.0p29 which may lead to unintended information disclosure through automatically generated user specific tags within Rest API documentation.

Affected Software

124 affected components
Tribe29 Checkmk=2.1.0
Tribe29 Checkmk=2.1.0-b1
Tribe29 Checkmk=2.1.0-b2
Tribe29 Checkmk=2.1.0-b3
Tribe29 Checkmk=2.1.0-b4
Tribe29 Checkmk=2.1.0-b5
Tribe29 Checkmk=2.1.0-b6
Tribe29 Checkmk=2.1.0-b7
Tribe29 Checkmk=2.1.0-b8
Tribe29 Checkmk=2.1.0-b9
Tribe29 Checkmk=2.1.0-p1
Tribe29 Checkmk=2.1.0-p10
Tribe29 Checkmk=2.1.0-p11
Tribe29 Checkmk=2.1.0-p12
Tribe29 Checkmk=2.1.0-p13
Tribe29 Checkmk=2.1.0-p2
Tribe29 Checkmk=2.1.0-p3
Tribe29 Checkmk=2.1.0-p4
Tribe29 Checkmk=2.1.0-p5
Tribe29 Checkmk=2.1.0-p6
Tribe29 Checkmk=2.1.0-p7
Tribe29 Checkmk=2.1.0-p8
Tribe29 Checkmk=2.1.0-p9
Tribe29 Checkmk=2.0.0
Tribe29 Checkmk=2.0.0-b1
Tribe29 Checkmk=2.0.0-b2
Tribe29 Checkmk=2.0.0-b3
Tribe29 Checkmk=2.0.0-b4
Tribe29 Checkmk=2.0.0-b5
Tribe29 Checkmk=2.0.0-b6
Tribe29 Checkmk=2.0.0-b7
Tribe29 Checkmk=2.0.0-b8
Tribe29 Checkmk=2.0.0-i1
Tribe29 Checkmk=2.0.0-p1
Tribe29 Checkmk=2.0.0-p10
Tribe29 Checkmk=2.0.0-p11
Tribe29 Checkmk=2.0.0-p12
Tribe29 Checkmk=2.0.0-p13
Tribe29 Checkmk=2.0.0-p14
Tribe29 Checkmk=2.0.0-p15
Tribe29 Checkmk=2.0.0-p16
Tribe29 Checkmk=2.0.0-p17
Tribe29 Checkmk=2.0.0-p18
Tribe29 Checkmk=2.0.0-p19
Tribe29 Checkmk=2.0.0-p2
Tribe29 Checkmk=2.0.0-p20
Tribe29 Checkmk=2.0.0-p21
Tribe29 Checkmk=2.0.0-p22
Tribe29 Checkmk=2.0.0-p23
Tribe29 Checkmk=2.0.0-p24
Tribe29 Checkmk=2.0.0-p25
Tribe29 Checkmk=2.0.0-p26
Tribe29 Checkmk=2.0.0-p27
Tribe29 Checkmk=2.0.0-p28
Tribe29 Checkmk=2.0.0-p29
Tribe29 Checkmk=2.0.0-p3
Tribe29 Checkmk=2.0.0-p4
Tribe29 Checkmk=2.0.0-p5
Tribe29 Checkmk=2.0.0-p6
Tribe29 Checkmk=2.0.0-p7
Tribe29 Checkmk=2.0.0-p8
Tribe29 Checkmk=2.0.0-p9
CheckMK Checkmk=2.1.0
CheckMK Checkmk=2.1.0-b1
CheckMK Checkmk=2.1.0-b2
CheckMK Checkmk=2.1.0-b3
CheckMK Checkmk=2.1.0-b4
CheckMK Checkmk=2.1.0-b5
CheckMK Checkmk=2.1.0-b6
CheckMK Checkmk=2.1.0-b7
CheckMK Checkmk=2.1.0-b8
CheckMK Checkmk=2.1.0-b9
CheckMK Checkmk=2.1.0-p1
CheckMK Checkmk=2.1.0-p10
CheckMK Checkmk=2.1.0-p11
CheckMK Checkmk=2.1.0-p12
CheckMK Checkmk=2.1.0-p13
CheckMK Checkmk=2.1.0-p2
CheckMK Checkmk=2.1.0-p3
CheckMK Checkmk=2.1.0-p4
CheckMK Checkmk=2.1.0-p5
CheckMK Checkmk=2.1.0-p6
CheckMK Checkmk=2.1.0-p7
CheckMK Checkmk=2.1.0-p8
CheckMK Checkmk=2.1.0-p9
CheckMK Checkmk=2.0.0
CheckMK Checkmk=2.0.0-b1
CheckMK Checkmk=2.0.0-b2
CheckMK Checkmk=2.0.0-b3
CheckMK Checkmk=2.0.0-b4
CheckMK Checkmk=2.0.0-b5
CheckMK Checkmk=2.0.0-b6
CheckMK Checkmk=2.0.0-b7
CheckMK Checkmk=2.0.0-b8
CheckMK Checkmk=2.0.0-i1
CheckMK Checkmk=2.0.0-p1
CheckMK Checkmk=2.0.0-p10
CheckMK Checkmk=2.0.0-p11
CheckMK Checkmk=2.0.0-p12
CheckMK Checkmk=2.0.0-p13
CheckMK Checkmk=2.0.0-p14
CheckMK Checkmk=2.0.0-p15
CheckMK Checkmk=2.0.0-p16
CheckMK Checkmk=2.0.0-p17
CheckMK Checkmk=2.0.0-p18
CheckMK Checkmk=2.0.0-p19
CheckMK Checkmk=2.0.0-p2
CheckMK Checkmk=2.0.0-p20
CheckMK Checkmk=2.0.0-p21
CheckMK Checkmk=2.0.0-p22
CheckMK Checkmk=2.0.0-p23
CheckMK Checkmk=2.0.0-p24
CheckMK Checkmk=2.0.0-p25
CheckMK Checkmk=2.0.0-p26
CheckMK Checkmk=2.0.0-p27
CheckMK Checkmk=2.0.0-p28
CheckMK Checkmk=2.0.0-p29
CheckMK Checkmk=2.0.0-p3
CheckMK Checkmk=2.0.0-p4
CheckMK Checkmk=2.0.0-p5
CheckMK Checkmk=2.0.0-p6
CheckMK Checkmk=2.0.0-p7
CheckMK Checkmk=2.0.0-p8
CheckMK Checkmk=2.0.0-p9

Event History

Feb 20, 2023
CVE Published
via MITRE·04:55 PM
Data Sourced
via MITRE·04:55 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2022-48318?

CVE-2022-48318 has not been assigned a CVSS score, but it is considered to potentially allow unintended information disclosure.

2

How do I fix CVE-2022-48318?

To mitigate CVE-2022-48318, update Checkmk to version 2.1.0p14 or later.

3

What are the affected versions for CVE-2022-48318?

CVE-2022-48318 affects Tribe29's Checkmk versions up to 2.1.0p13 and 2.0.0p29.

4

What impact does CVE-2022-48318 have?

CVE-2022-48318 can lead to unintended information disclosure through user-specific tags in the Rest API documentation.

5

Are authorization controls in the RestAPI documentation affected by CVE-2022-48318?

Yes, CVE-2022-48318 indicates that there are no authorization controls in the RestAPI documentation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203