dbcve.org
CheckmkApplication

CVE-2024-28826

HIGH · 8.1 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to after 2.0.0 or later.
See remediation →
87/100
Remediation priority · High
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 restriction of local upload and download paths in check_sftp in Checkmk before 2.3.0p4, 2.2.0p27, 2.1.0p44, and in Checkmk 2.0.0 (EOL) allows attackers with sufficient permissions to configure the check to read and write local files on the Checkmk site server.

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 path traversal vulnerability in Checkmk's check_sftp component where improper restriction of local upload and download paths allows authenticated users with sufficient permissions to read and write arbitrary files on the Checkmk server via the SFTP check configuration.

MitigationUpgrade to Checkmk versions 2.3.0p4, 2.2.0p27, 2.1.0p44 or later. Until patched, restrict administrative permissions for users who can configure SFTP checks.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 'Help > About' to find the exact version number
    Affected if The version is 2.0.0 or earlier, or exactly 2.1.0, 2.2.0, or 2.3.0 (not patched to 2.3.0p4, 2.2.0p27, or 2.1.0p44)
  2. Verify SFTP check functionality is in use
    Navigate to the Checkmk web interface > Setup > Services > Monitored endpoints > SFTP checks, or run 'cmk -L' to list available check types and look for 'check_sftp'
    Affected if SFTP checks are configured and active in the monitoring environment
  3. Review SFTP check configuration
    Access Setup > Services > Monitored endpoints > SFTP checks and inspect any configured SFTP check definitions for path parameters
    Affected if Any SFTP check configurations exist that could accept file paths
  4. Audit user permissions for SFTP configuration
    Go to Setup > Users > Roles and Permissions > Permission settings, or check the 'Checkmk: SFTP checks' permission category under the relevant user roles
    Affected if Any user role grants permission to configure or edit SFTP checks
  5. Examine SFTP connection logging
    Check Checkmk's var/log directory for SFTP-related log files, or view the SFTP check output in the GUI for any unusual path access attempts
    Affected if Logs show unexpected file paths being accessed via SFTP functionality

You are affected if your Checkmk version is within the affected range AND the SFTP check feature is enabled with users having SFTP configuration permissions.

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 a release after 2.0.0
Interim mitigation

Upgrade to Checkmk versions 2.3.0p4, 2.2.0p27, 2.1.0p44 or later. Until patched, restrict administrative permissions for users who can configure SFTP checks.

Recommended fix High confidence

2.3.0p4 (or later 2.3.x), 2.2.0p27 (or later 2.2.x), or 2.1.0p44 (or later 2.1.x); 2.0.0 is EOL with no patch

  1. 1. Identify current Checkmk version by running 'cmk --version' or checking the GUI login page
  2. 2. Determine which version branch you are on (2.1.x, 2.2.x, or 2.3.x)
  3. 3. For Checkmk 2.3.x: Upgrade to version 2.3.0p4 or later
  4. 4. For Checkmk 2.2.x: Upgrade to version 2.2.0p27 or later
  5. 5. For Checkmk 2.1.x: Upgrade to version 2.1.0p44 or later
  6. 6. For Checkmk 2.0.0: This version is End-of-Life (EOL) with no patch available; migrate to a supported version
  7. 7. After upgrade, verify the check_sftp configuration does not contain malicious path traversal patterns
  8. 8. Review user permissions for check_sftp rule configuration to ensure only trusted admins can configure it
Caveat Standard Checkmk upgrade procedures apply; always backup configuration before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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