dbcve.org
CheckmkApplication

CVE-2024-38865

HIGH · 8.8 CVSS v3.1 Published 2025-04-10
Fix available
A fix is available. Upgrade to 2.1.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Improper neutralization of livestatus command delimiters in a specific endpoint within RestAPI of Checkmk prior to 2.2.0p39, 2.3.0p25, and 2.1.0p51 (EOL) allows arbitrary livestatus command execution. Exploitation requires the attacker to have a contact group assigned to their user account and for an event to originate from a host with the same contact group or from an event generated with an unknown host.

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

Improper neutralization of livestatus command delimiters in the Checkmk RestAPI allows authenticated users with contact group assignments to execute arbitrary livestatus commands. The attack requires an event originating from a host sharing the same contact group or from an unknown host, enabling command injection through unsanitized input handling.

MitigationUpdate Checkmk to version 2.2.0p39, 2.3.0p25, or later to patch the livestatus command injection vulnerability. Restrict RestAPI access to trusted users and review contact group assignments.

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.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 the installed Checkmk version
    Run 'cmk --version' or check the Checkmk web interface under 'Help > About' to determine the exact version number
    Affected if The installed version is less than 2.1.0, or exactly 2.1.0, 2.2.0, or 2.3.0
  2. Verify if the RestAPI is enabled
    Check the Checkmk configuration files (typically in /opt/omd/sites/<site>/etc/apache/conf.d/ or via the web interface under 'Setup > General > API') to confirm the RestAPI is active
    Affected if The RestAPI is enabled and accessible
  3. Identify RestAPI users with contact group assignments
    Review user configurations in 'Setup > Users' via the web interface or query the contacts configuration to identify which RestAPI-authenticated users belong to contact groups
    Affected if There are authenticated RestAPI users assigned to contact groups
  4. Inventory hosts assigned to contact groups
    Check host configuration in 'Setup > Hosts' to identify which hosts share contact groups with RestAPI users, or verify if there are hosts with no explicit contact group assignment (unknown hosts)
    Affected if Hosts exist that share contact groups with RestAPI users, or unknown/unassigned hosts are present

Your environment is affected if you run a vulnerable Checkmk version (2.1.0, 2.2.0, 2.3.0, or pre-2.1.0) with the RestAPI enabled and have users with contact group assignments who can trigger livestatus commands through host events.

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.1.0 or later
Fixed in 2.1.0
Interim mitigation

Update Checkmk to version 2.2.0p39, 2.3.0p25, or later to patch the livestatus command injection vulnerability. Restrict RestAPI access to trusted users and review contact group assignments.

Recommended fix High confidence

2.2.0p39 or later for 2.2.x; 2.3.0p25 or later for 2.3.x; migrate from 2.1.x to 2.2.x or 2.3.x as 2.1.x is EOL

  1. 1. Identify current Checkmk installation version using 'cmk --version' or the web interface version display
  2. 2. Determine which major version branch you are running (2.1.x, 2.2.x, or 2.3.x)
  3. 3. If running 2.1.x: Plan migration to 2.2.x or 2.3.x as 2.1.0p51 is marked EOL (End of Life)
  4. 4. If running 2.2.x: Upgrade to version 2.2.0p39 or later within the 2.2 branch
  5. 5. If running 2.3.x: Upgrade to version 2.3.0p25 or later within the 2.3 branch
  6. 6. Perform a full backup of the Checkmk configuration and database before upgrading
  7. 7. Test the upgrade in a non-production environment first
  8. 8. Apply the upgrade following Checkmk's standard upgrade procedure
Caveat Review Checkmk release notes for breaking changes between versions; ensure contact group configuration is preserved after upgrade; test thoroughly in staging before production deployment

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,460
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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