dbcve.org
CheckmkApplication

CVE-2024-38863

HIGH · 7.5 CVSS v3.1 Published 2024-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Exposure of CSRF tokens in query parameters on specific requests in Checkmk GmbH's Checkmk versions <2.3.0p18, <2.2.0p35 and <2.1.0p48 could lead to a leak of the token to facilitate targeted phishing attacks.

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

This vulnerability in Checkmk exposes CSRF tokens in URL query parameters for certain requests. CSRF tokens should typically be transmitted via POST body or custom headers, not in URLs where they can be logged in server access logs, browser history, and potentially leaked via HTTP referrer headers. Attackers who obtain these exposed tokens could craft targeted phishing attacks to perform unauthorized actions on behalf of authenticated users.

MitigationUpgrade Checkmk to version 2.3.0p18, 2.2.0p35, or 2.1.0p48 or later to receive the patch that removes CSRF tokens from query parameters.

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.2.0= 2.3.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the command to display the Checkmk version, typically via 'cmk --version' or check the web interface footer for the version number
    Affected if The installed version matches 2.1.0, 2.2.0, or 2.3.0 exactly (not patched point releases)
  2. Verify if CSRF tokens appear in URL query parameters
    Use browser developer tools or a proxy to intercept HTTP requests and examine whether URLs contain CSRF tokens as query parameters (e.g., ?csrf_token=...)
    Affected if CSRF tokens are transmitted via URL query parameters rather than POST body or custom headers
  3. Check server access logs for CSRF token exposure
    Review Checkmk server access logs for entries containing 'csrf_token' in the requested URL query strings
    Affected if CSRF tokens are logged in server access logs, indicating exposure through the vulnerability

You are affected if you are running Checkmk versions 2.1.0, 2.2.0, or 2.3.0 (excluding their patched point releases) and your application's CSRF tokens are being transmitted in URL query parameters.

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 Checkmk to version 2.3.0p18, 2.2.0p35, or 2.1.0p48 or later to receive the patch that removes CSRF tokens from query parameters.

Recommended fix High confidence

2.3.0p18 (or later) for v2.3.x; 2.2.0p35 (or later) for v2.2.x; 2.1.0p48 (or later) for v2.1.x

  1. Identify the currently installed Checkmk version using the Checkmk web interface or command line
  2. Determine which major version branch (2.1.0, 2.2.0, or 2.3.0) is currently in use
  3. Download the appropriate patched release for your version branch from checkmk.com (2.1.0p48 or later, 2.2.0p35 or later, or 2.3.0p18 or later)
  4. Follow Checkmk's standard upgrade procedure: stop the site, run the setup script, and restart the site
  5. Verify the installation by checking the version number in the web interface
  6. Log out and log back in to ensure new CSRF tokens are generated

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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