CVE-2022-48317: Insecure Termination of RestAPI Session Tokens

Published Feb 20, 2023
·
Updated

Expired sessions were not securely terminated in the RestAPI for Tribe29's Checkmk <= 2.1.0p10 and Checkmk <= 2.0.0p28 allowing an attacker to use expired session tokens when communicating with the RestAPI.

Affected Software

116 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-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-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-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-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 vulnerability associated with CVE-2022-48317?

CVE-2022-48317 describes a security issue in Tribe29's Checkmk versions <= 2.1.0p10 and <= 2.0.0p28 where expired sessions are not securely terminated, allowing attackers to exploit expired session tokens.

2

How do I fix CVE-2022-48317?

To mitigate CVE-2022-48317, upgrade to a version of Checkmk above 2.1.0p10 or 2.0.0p28 where this vulnerability has been addressed.

3

What affected versions of Checkmk are listed in CVE-2022-48317?

CVE-2022-48317 affects Checkmk versions 2.1.0 through 2.1.0p10 and 2.0.0 through 2.0.0p28.

4

What type of attack is possible through CVE-2022-48317?

An attacker can exploit CVE-2022-48317 by using expired session tokens to communicate with the RestAPI.

5

What security risk does CVE-2022-48317 present?

CVE-2022-48317 poses a risk of unauthorized access to sensitive information as attackers can misuse expired session tokens.

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