dbcve.org
CheckmkApplication

CVE-2024-6572

HIGH · 7.4 CVSS v3.1 Published 2024-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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 host key checking in active check 'Check SFTP Service' and special agent 'VNX quotas and filesystem' in Checkmk before Checkmk 2.3.0p15, 2.2.0p33, 2.1.0p48 and 2.0.0 (EOL) allows man-in-the-middle attackers to intercept traffic

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

Checkmk versions prior to 2.3.0p15, 2.2.0p33, and 2.1.0p48 contain improper host key verification in the 'Check SFTP Service' active check and 'VNX quotas and filesystem' special agent, enabling man-in-the-middle attackers to intercept SFTP traffic by impersonating the target server.

MitigationUpgrade Checkmk to version 2.3.0p15, 2.2.0p33, 2.1.0p48 or later. For EOL version 2.0.0, migrate to a supported version. After upgrading, verify SFTP monitoring checks function correctly.

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 installed Checkmk version
    Run 'cmk --version' or check the Checkmk web interface under 'User profile > About Checkmk' to determine the exact version number
    Affected if Version is 2.3.0p14 or earlier, 2.2.0p32 or earlier, 2.1.0p47 or earlier, or any 2.0.0 version
  2. Check for active SFTP Service checks
    In Checkmk web UI, go to 'Setup > Services > Other services' or search for 'Check SFTP Service' in the service catalog. Also inspect the ~/var/check_mk/crashes directory for SFTP-related crash logs
    Affected if Any SFTP Service active check is configured and enabled
  3. Check for VNX quotas special agent usage
    In Checkmk web UI, go to 'Setup > Agents > VM, Cloud, Container > VNX Quotas and Filesystem' or search for VNX in the special agents section. Review any host configured with the VNX quotas agent
    Affected if The VNX quotas and filesystem special agent is configured on any host
  4. Verify SFTP host key configuration
    Examine the SFTP check configuration file (typically in ~/etc/check_mk/conf.d/ or via web UI) for the specific SFTP server entry and confirm whether strict host key checking is enabled or disabled
    Affected if Host key verification is disabled, or the configuration shows 'strict_host_key_checking' set to 'no' or omitted entirely

You are affected if your Checkmk version falls within the vulnerable ranges AND you have either SFTP Service active checks or VNX quotas special agents configured with host key verification disabled or not properly set.

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.0p15, 2.2.0p33, 2.1.0p48 or later. For EOL version 2.0.0, migrate to a supported version. After upgrading, verify SFTP monitoring checks function correctly.

Recommended fix High confidence

2.3.0p15 (or latest 2.3.x), 2.2.0p33 (or latest 2.2.x), 2.1.0p48 (or latest 2.1.x), or migrate off EOL 2.0.0 to a supported branch

  1. 1. Identify the current Checkmk version by running 'cmk --version' or checking the web interface version info.
  2. 2. Based on your current version branch, determine the minimum required patch version: For 2.3.x users, upgrade to 2.3.0p15 or later. For 2.2.x users, upgrade to 2.2.0p33 or later. For 2.1.x users, upgrade to 2.1.0p48 or later. For 2.0.x users, note that 2.0.0 is End-of-Life (EOL) with no patch; upgrade to a supported branch (2.1, 2.2, or 2.3).
  3. 3. Before upgrading, review the Checkmk release notes for the target version to check for any relevant changes or known issues.
  4. 4. Perform the upgrade using your preferred method (omd upgrade, package manager, or manual update).
  5. 5. After upgrade, verify the SFTP and VNX agent configurations to ensure host key checking is now properly enforced.
  6. 6. Test the SFTP active check and VNX special agent in a non-production environment before deploying to production.
Caveat Patch updates within the same minor version (e.g., 2.3.0 to 2.3.0p15) typically have minimal breaking changes; however, 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
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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