dbcve.org
CheckmkApplication

CVE-2022-48318

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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
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.

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 · moderate confidence

The Checkmk REST API documentation lacks proper authorization controls, allowing unauthenticated or unauthorized users to access automatically generated user-specific tags within the API documentation. This exposes sensitive information about users through the documentation interface.

MitigationImplement proper authorization checks on the REST API documentation endpoint to ensure only authenticated and authorized users can access user-specific documentation content.

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
Low
Integrity
None
Availability
None

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

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 'cmk --version' or check the Checkmk web interface (About page) to determine the exact version number
    Affected if The installed version is exactly 2.0.0 or exactly 2.1.0
  2. Locate the REST API documentation endpoint
    Access the Checkmk web interface and navigate to the REST API documentation section (typically found under Help > REST API or similar documentation links)
    Affected if The documentation page loads without requiring authentication or explicit authorization for access
  3. Verify authorization requirements on API documentation
    Attempt to access the REST API documentation URL from an unauthenticated browser session (incognito/private window) or via curl without authentication headers
    Affected if The documentation content is served without redirecting to a login page or returning an authentication error (HTTP 401)
  4. Check for user-specific information exposure
    Examine the REST API documentation page for any automatically generated user-specific tags, usernames, or sensitive configuration details that would only be visible to authenticated users
    Affected if User-specific tags, internal user identifiers, or sensitive user-related information is visible in the documentation

You are affected if running Checkmk version 2.0.0 or 2.1.0 AND the REST API documentation endpoint is accessible without authentication, exposing user-specific information to unauthenticated users.

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

Implement proper authorization checks on the REST API documentation endpoint to ensure only authenticated and authorized users can access user-specific documentation content.

Recommended fix Moderate confidence

Checkmk 2.1.0p14 or later / Checkmk 2.0.0p30 or later

  1. 1. Identify your current Checkmk version by navigating to the 'Help' > 'About Checkmk' page in the web interface.
  2. 2. If running Checkmk 2.1.0, verify the patch version (pX). If running version 2.1.0p13 or earlier, plan for upgrade.
  3. 3. If running Checkmk 2.0.0, verify the patch version. If running version 2.0.0p29 or earlier, plan for upgrade.
  4. 4. Before upgrading, backup your Checkmk configuration and data following standard backup procedures.
  5. 5. Download Checkmk version 2.1.0p14 or later (for 2.x users), or obtain the equivalent fixed release from Checkmk's official download portal.
  6. 6. Apply the upgrade following Checkmk's standard upgrade documentation for your installation method (RAW, CRE, or CEE).
  7. 7. After upgrade, verify the RestAPI documentation is no longer exposing user-specific tags without authorization.
Caveat Review Checkmk 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-48318 — 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-48318 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