dbcve.org
CheckmkApplication

CVE-2024-38859

MEDIUM · 6.1 CVSS v3.1 Published 2024-08-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
XSS in the view page with the SLA column configured in Checkmk versions prior to 2.3.0p14, 2.2.0p33, 2.1.0p47 and 2.0.0 (EOL) allowed malicious users to execute arbitrary scripts by injecting HTML elements into the SLA column title. These scripts could be executed when the view page was cloned by other users.

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

Stored XSS vulnerability in Checkmk's view page where malicious users can inject arbitrary HTML/JavaScript into the SLA column title. When other users clone the affected view page, the injected scripts execute in their browser context.

MitigationUpgrade to Checkmk versions 2.3.0p14, 2.2.0p33, or 2.1.0p47 or later. For EOL version 2.0.0, upgrade to a supported release. The fix requires proper input sanitization and output encoding of the SLA column title field.

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.0.0= 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Checkmk version
    Run command: omd version or check the GUI at User > About Checkmk. Alternatively, check /omd/versions/ directory.
    Affected if Version is 2.0.0, 2.1.0, 2.2.0, or 2.3.0 (any patch level below the fixed versions)
  2. Locate custom or cloned views with SLA columns
    Navigate to Setup > Views or inspect the views configuration files in ~/var/check_mk/web/views/ directory. Look for views containing the 'sla' column definition.
    Affected if Custom or cloned views exist that include an SLA column configuration
  3. Inspect SLA column title values for injected scripts
    For each view with an SLA column, examine the column configuration. Check the 'title' or 'column_title' parameter for HTML/JavaScript content such as <script>, onload, onerror, or javascript: URLs.
    Affected if The SLA column title contains unsanitized HTML tags, event handlers, or script URLs
  4. Check view export files for malicious content
    Examine view configuration files in etc/check_mk/conf.d/wato/ or the views.mk files for any SLA column definitions with suspicious title values.
    Affected if View configuration contains unexpected HTML or script tags in SLA column settings

A user is affected if running a vulnerable Checkmk version (2.0.0-2.3.0) AND has views with custom SLA column titles that contain injected HTML or JavaScript code.

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 versions 2.3.0p14, 2.2.0p33, or 2.1.0p47 or later. For EOL version 2.0.0, upgrade to a supported release. The fix requires proper input sanitization and output encoding of the SLA column title field.

Recommended fix High confidence

Upgrade to 2.3.0p14 (for 2.3.x line), 2.2.0p33 (for 2.2.x line), or 2.1.0p47 (for 2.1.x line); migrate off 2.0.x to a supported version as it is EOL

  1. Identify the current Checkmk version in use (check via 'cmk --version' or the web UI footer)
  2. Determine the appropriate upgrade path based on the major version line (2.0.x, 2.1.x, 2.2.x, or 2.3.x)
  3. For Checkmk 2.3.x: Upgrade to version 2.3.0p14 or later
  4. For Checkmk 2.2.x: Upgrade to version 2.2.0p33 or later
  5. For Checkmk 2.1.x: Upgrade to version 2.1.0p47 or later
  6. For Checkmk 2.0.x: Note that 2.0.0 is End-of-Life (EOL); plan migration to a supported version line
  7. After upgrade, verify the fix by confirming the version number in the web UI or via 'cmk --version'
  8. Test that SLA column functionality works correctly after upgrade
Caveat Checkmk 2.0.x is End-of-Life with no patch available - migration to 2.1.x, 2.2.x, or 2.3.x required; review Checkmk release notes for any breaking changes between major versions

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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