dbcve.org
CheckmkApplication

CVE-2024-2380

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

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
Stored XSS in graph rendering in Checkmk <2.3.0b4.

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

A stored Cross-Site Scripting (XSS) vulnerability exists in the graph rendering component of Checkmk monitoring platform versions prior to 2.3.0b4. Attackers can inject malicious JavaScript code through graph data that gets stored and executed when other users view the rendered graphs.

MitigationUpgrade Checkmk to version 2.3.0b4 or later to patch the stored XSS vulnerability in graph rendering.

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

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Determine installed Checkmk version
    Run 'cmk --version' or 'omd version' from the Checkmk server command line, or log into the Checkmk web interface and check the version information typically displayed in the footer or about page
    Affected if The version shown is 2.3.0 or any version prior to 2.3.0b4 (such as 2.2.0p系列)
  2. Verify graph rendering access
    Confirm that the Checkmk web interface is accessible and that users have permissions to view monitoring graphs through the graphs module or dashboard
    Affected if The graph rendering component is enabled and accessible to users in the environment
  3. Inspect stored graph data
    Check the Checkmk database or graph configuration storage for any graph definitions or stored metrics that may contain unexpected script tags or JavaScript code in data fields
    Affected if Graph data storage contains suspicious entries with script tags, javascript: URIs, or other XSS payload patterns in fields that get rendered
  4. Review recent graph creation or modification activity
    Examine audit logs, graph history, or configuration change logs for any recent additions or modifications to graph definitions that contain unusual data patterns
    Affected if Recent graph-related entries show unexpected encoded content or patterns consistent with injection attempts

You are affected if your Checkmk installation is version 2.3.0 or any version prior to 2.3.0b4 AND the graph rendering component is enabled and accessible to users who could potentially inject or view stored graph data.

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.0b4 or later to patch the stored XSS vulnerability in graph rendering.

Recommended fix Moderate confidence

2.3.0b4 or later stable release

  1. 1. Identify current Checkmk version by checking the installation
  2. 2. Download Checkmk version 2.3.0b4 or a later stable version from the official Checkmk download page (checkmk.com)
  3. 3. Review Checkmk upgrade documentation for your specific installation type (raw, enterprise, or managed)
  4. 4. Create a full backup of the current Checkmk installation and configuration
  5. 5. Stop the Checkmk site before upgrading
  6. 6. Install the upgraded Checkmk package using the appropriate package manager for your OS (deb, rpm, or tar)
  7. 7. Start the Checkmk site and verify the upgrade completed successfully
  8. 8. Test the graph rendering functionality to confirm the XSS vulnerability is resolved
Caveat Review Checkmk release notes for 2.3.0b4 to check for any breaking changes in graph rendering or related components; beta versions may have additional risks

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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