dbcve.org
CheckmkApplication

CVE-2024-6542

MEDIUM · 6.5 CVSS v3.1 Published 2024-07-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
Improper neutralization of livestatus command delimiters in mknotifyd in Checkmk <= 2.0.0p39, < 2.1.0p47, < 2.2.0p32 and < 2.3.0p11 allows arbitrary livestatus command execution.

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

A command injection vulnerability exists in the mknotifyd component of Checkmk where livestatus command delimiters are not properly neutralized, allowing authenticated attackers to execute arbitrary livestatus commands.

MitigationUpgrade Checkmk to version 2.0.0p40, 2.1.0p47, 2.2.0p32, 2.3.0p11 or later. If immediate patching is not possible, restrict access to the mknotifyd interface and livestatus API.

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
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 footer for the version number
    Affected if The installed version is 2.0.0, 2.1.0, 2.2.0, or 2.3.0 (prior to the patched releases: 2.0.0p40, 2.1.0p47, 2.2.0p32, 2.3.0p11)
  2. Determine if mknotifyd component is active
    Check if the mknotifyd service or daemon process is running on the Checkmk server, or verify its configuration is present in the Checkmk setup
    Affected if mknotifyd is installed and enabled on the Checkmk instance
  3. Verify livestatus API accessibility
    Check if the livestatus module is enabled and reachable, typically via the Checkmk configuration or by attempting a livestatus query through the socket or API endpoint
    Affected if Livestatus is enabled and accessible to authenticated users (the vulnerability requires authenticated access to livestatus)
  4. Confirm user authentication scope for livestatus
    Review the Checkmk user permissions andlivestatus access controls to determine which users can send livestatus commands
    Affected if Any authenticated user has livestatus command execution privileges, as the flaw allows arbitrary livestatus commands by authenticated attackers

You are affected if your Checkmk version falls within 2.0.0 through the patch levels for each branch AND mknotifyd is enabled AND livestatus is 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Checkmk to version 2.0.0p40, 2.1.0p47, 2.2.0p32, 2.3.0p11 or later. If immediate patching is not possible, restrict access to the mknotifyd interface and livestatus API.

Recommended fix High confidence

Upgrade to Checkmk 2.0.0p39, 2.1.0p47, 2.2.0p32, or 2.3.0p11 depending on your current major version

  1. Identify your current Checkmk version using 'cmk --version' or the web UI
  2. Backup your Checkmk configuration and data before applying any update
  3. Download the appropriate patched version for your current release: for 2.0.0.x upgrade to 2.0.0p39, for 2.1.0.x upgrade to 2.1.0p47, for 2.2.0.x upgrade to 2.2.0p32, or for 2.3.0.x upgrade to 2.3.0p11
  4. Install the patched version using your deployment method (omd update, package manager, or manual update)
  5. Verify the update was successful by checking the version number
  6. Restart the mknotifyd service or the entire Checkmk site to ensure the patch takes effect
  7. Confirm the vulnerability is remediated by verifying the mknotifyd process no longer accepts improperly neutralized livestatus command delimiters
Caveat Standard patch updates typically do not introduce breaking changes but always review release notes before upgrading

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

Fix this in Checkmk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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