CWE
613
Advisory Published
Updated

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

First published: Mon 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.

Credit: security@checkmk.com

Affected SoftwareAffected VersionHow to fix
Checkmk NagVis=2.1.0
Checkmk NagVis=2.1.0-b1
Checkmk NagVis=2.1.0-b2
Checkmk NagVis=2.1.0-b3
Checkmk NagVis=2.1.0-b4
Checkmk NagVis=2.1.0-b5
Checkmk NagVis=2.1.0-b6
Checkmk NagVis=2.1.0-b7
Checkmk NagVis=2.1.0-b8
Checkmk NagVis=2.1.0-b9
Checkmk NagVis=2.1.0-p1
Checkmk NagVis=2.1.0-p10
Checkmk NagVis=2.1.0-p2
Checkmk NagVis=2.1.0-p3
Checkmk NagVis=2.1.0-p4
Checkmk NagVis=2.1.0-p5
Checkmk NagVis=2.1.0-p6
Checkmk NagVis=2.1.0-p7
Checkmk NagVis=2.1.0-p8
Checkmk NagVis=2.1.0-p9
Checkmk NagVis=2.0.0
Checkmk NagVis=2.0.0-b1
Checkmk NagVis=2.0.0-b2
Checkmk NagVis=2.0.0-b3
Checkmk NagVis=2.0.0-b4
Checkmk NagVis=2.0.0-b5
Checkmk NagVis=2.0.0-b6
Checkmk NagVis=2.0.0-b7
Checkmk NagVis=2.0.0-b8
Checkmk NagVis=2.0.0-i1
Checkmk NagVis=2.0.0-p1
Checkmk NagVis=2.0.0-p10
Checkmk NagVis=2.0.0-p11
Checkmk NagVis=2.0.0-p12
Checkmk NagVis=2.0.0-p13
Checkmk NagVis=2.0.0-p14
Checkmk NagVis=2.0.0-p15
Checkmk NagVis=2.0.0-p16
Checkmk NagVis=2.0.0-p17
Checkmk NagVis=2.0.0-p18
Checkmk NagVis=2.0.0-p19
Checkmk NagVis=2.0.0-p2
Checkmk NagVis=2.0.0-p20
Checkmk NagVis=2.0.0-p21
Checkmk NagVis=2.0.0-p22
Checkmk NagVis=2.0.0-p23
Checkmk NagVis=2.0.0-p24
Checkmk NagVis=2.0.0-p25
Checkmk NagVis=2.0.0-p26
Checkmk NagVis=2.0.0-p27
Checkmk NagVis=2.0.0-p28
Checkmk NagVis=2.0.0-p3
Checkmk NagVis=2.0.0-p4
Checkmk NagVis=2.0.0-p5
Checkmk NagVis=2.0.0-p6
Checkmk NagVis=2.0.0-p7
Checkmk NagVis=2.0.0-p8
Checkmk NagVis=2.0.0-p9
Checkmk NagVis=2.1.0
Checkmk NagVis=2.1.0-b1
Checkmk NagVis=2.1.0-b2
Checkmk NagVis=2.1.0-b3
Checkmk NagVis=2.1.0-b4
Checkmk NagVis=2.1.0-b5
Checkmk NagVis=2.1.0-b6
Checkmk NagVis=2.1.0-b7
Checkmk NagVis=2.1.0-b8
Checkmk NagVis=2.1.0-b9
Checkmk NagVis=2.1.0-p1
Checkmk NagVis=2.1.0-p10
Checkmk NagVis=2.1.0-p2
Checkmk NagVis=2.1.0-p3
Checkmk NagVis=2.1.0-p4
Checkmk NagVis=2.1.0-p5
Checkmk NagVis=2.1.0-p6
Checkmk NagVis=2.1.0-p7
Checkmk NagVis=2.1.0-p8
Checkmk NagVis=2.1.0-p9
Checkmk NagVis=2.0.0
Checkmk NagVis=2.0.0-b1
Checkmk NagVis=2.0.0-b2
Checkmk NagVis=2.0.0-b3
Checkmk NagVis=2.0.0-b4
Checkmk NagVis=2.0.0-b5
Checkmk NagVis=2.0.0-b6
Checkmk NagVis=2.0.0-b7
Checkmk NagVis=2.0.0-b8
Checkmk NagVis=2.0.0-i1
Checkmk NagVis=2.0.0-p1
Checkmk NagVis=2.0.0-p10
Checkmk NagVis=2.0.0-p11
Checkmk NagVis=2.0.0-p12
Checkmk NagVis=2.0.0-p13
Checkmk NagVis=2.0.0-p14
Checkmk NagVis=2.0.0-p15
Checkmk NagVis=2.0.0-p16
Checkmk NagVis=2.0.0-p17
Checkmk NagVis=2.0.0-p18
Checkmk NagVis=2.0.0-p19
Checkmk NagVis=2.0.0-p2
Checkmk NagVis=2.0.0-p20
Checkmk NagVis=2.0.0-p21
Checkmk NagVis=2.0.0-p22
Checkmk NagVis=2.0.0-p23
Checkmk NagVis=2.0.0-p24
Checkmk NagVis=2.0.0-p25
Checkmk NagVis=2.0.0-p26
Checkmk NagVis=2.0.0-p27
Checkmk NagVis=2.0.0-p28
Checkmk NagVis=2.0.0-p3
Checkmk NagVis=2.0.0-p4
Checkmk NagVis=2.0.0-p5
Checkmk NagVis=2.0.0-p6
Checkmk NagVis=2.0.0-p7
Checkmk NagVis=2.0.0-p8
Checkmk NagVis=2.0.0-p9

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203