dbcve.org
CheckmkApplication

CVE-2022-48317

CRITICAL · 9.8 CVSS v3.1 Published 2023-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Checkmk RestAPI fails to securely terminate expired sessions, allowing attackers to continue using session tokens after their intended expiration time. This session management flaw in versions <= 2.1.0p10 and <= 2.0.0p28 permits unauthorized API access via replay of expired but still-valid session credentials.

MitigationUpgrade to Checkmk 2.1.0p11 or 2.0.0p28 or later to patch the session termination vulnerability. Until patched, restrict RestAPI access to trusted networks or implement additional authentication layers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CheckmkApplication
Affected:= 2.1.0= 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Checkmk version
    Run `omd version` or `cmk --version` on the Checkmk server to determine the exact installed version
    Affected if Version is 2.1.0p10 or lower, or 2.0.0p28 or lower
  2. Confirm RestAPI is enabled
    Check for API access endpoint at /check_mk/api/ or review Checkmk site configuration for rest_api service enabled via `cmk -L` or site management
    Affected if RestAPI module is active and accessible
  3. Locate session configuration
    Inspect the Checkmk site etc directory (typically /omd/sites/<sitename>/etc/check_mk/conf.d/) or the main mk_confi file for session timeout settings
    Affected if Session timeout is configured but tokens remain valid past expiration time (verify by testing with an expired token)
  4. Review active API sessions
    Query the RestAPI endpoint /check_mk/api/1.0/domain_types/authentication_sessions/collections/all or check user session list via web interface to see active sessions
    Affected if Expired session tokens are still returned as valid or can be reused

The environment is affected if running Checkmk 2.1.0p10 or earlier or 2.0.0p28 or earlier AND the RestAPI is enabled, with expired session tokens still functioning.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Checkmk 2.1.0p11 or 2.0.0p28 or later to patch the session termination vulnerability. Until patched, restrict RestAPI access to trusted networks or implement additional authentication layers.

Recommended fix Moderate confidence

Checkmk 2.0.0p28 or later, or 2.1.0p10 or later (or latest stable 2.1.x/2.2.x)

  1. 1. Identify your current Checkmk installation version using 'cmk --version' or through the web interface.
  2. 2. If running Checkmk 2.0.0, upgrade to version 2.0.0p28 or later.
  3. 3. If running Checkmk 2.1.0, upgrade to version 2.1.0p10 or later.
  4. 4. Alternatively, upgrade to the latest stable Checkmk 2.1.x or 2.2.x release which contains the fix.
  5. 5. After upgrade, verify the fix by checking that expired RestAPI session tokens are properly rejected.
  6. 6. Consider revoking any potentially compromised session tokens as a precautionary measure.
Caveat Review release notes for any breaking changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-48317 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data