dbcve.org
CheckmkApplication

CVE-2024-38858

MEDIUM · 6.1 CVSS v3.1 Published 2024-09-02
Fix available
A fix is available. Upgrade to 2.3.0 or later.
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
Improper neutralization of input in Checkmk before version 2.3.0p14 allows attackers to inject and run malicious scripts in the Robotmk logs view.

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 is a stored Cross-Site Scripting (XSS) vulnerability in Checkmk's Robotmk component. The logs view fails to properly sanitize or encode user-supplied input, allowing authenticated attackers to inject and execute malicious JavaScript code in the context of other users viewing the logs.

MitigationUpgrade Checkmk to version 2.3.0p14 or later to obtain the vendor patch that addresses proper input neutralization in the Robotmk logs view.

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.3.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 your Checkmk version
    Access the Checkmk web interface and navigate to Setup > General > About Checkmk, or run 'cmk --version' on the command line
    Affected if The version is listed as less than 2.3.0 or exactly 2.3.0 (e.g., 2.2.0, 2.3.0p0-p13)
  2. Confirm Robotmk extension is installed
    Navigate to Setup > Extensions > Plugins or check for the Robotmk package in your Checkmk installation directory (typically /omd/sites/<sitename>/local/lib/check_mk/plugins/)
    Affected if The Robotmk plugin files exist in your Checkmk installation
  3. Verify Robotmk is configured and active
    Navigate to Setup > Services > Monitored services and search for Robotmk-related services, or check the Robotmk configuration at Setup > Datasource programs > Robotmk
    Affected if Robotmk is actively collecting data or has saved configurations
  4. Check if Robotmk logs view is accessible
    Navigate to the Robotmk logs view in the Checkmk interface (typically via the Robotmk dashboard or logs section accessible to authenticated users)
    Affected if The logs view page loads and displays log entries

Your environment is affected if you run any Checkmk version below 2.3.0 or exactly 2.3.0 AND have the Robotmk extension installed with its logs view accessible to authenticated 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
Upgrade available Upgrade to 2.3.0 or later
Fixed in 2.3.0
Interim mitigation

Upgrade Checkmk to version 2.3.0p14 or later to obtain the vendor patch that addresses proper input neutralization in the Robotmk logs view.

Recommended fix High confidence

2.3.0p14 or later

  1. 1. Identify the current Checkmk version by running `cmk --version` or checking the Checkmk web interface.
  2. 2. Create a full backup of the Checkmk installation including configuration and site data.
  3. 3. Download Checkmk version 2.3.0p14 or a later stable release from the official Checkmk download page (checkmk.com).
  4. 4. Install the upgrade following Checkmk's standard upgrade procedure: `cmk -P install <package_file>` or use the web-based update mechanism.
  5. 5. Verify the upgrade was successful by checking the version again.
  6. 6. Test that the Robotmk logs view functions correctly and that the XSS vulnerability is remediated.
Caveat Point releases (e.g., 2.3.0p14) typically maintain backward compatibility; review release notes for any specific migration notes

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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