CVE-2024-28827
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 · uneditedIncorrect permissions on the Checkmk Windows Agent's data directory in Checkmk < 2.3.0p8, < 2.2.0p29, < 2.1.0p45, and <= 2.0.0p39 (EOL) allows a local attacker to gain SYSTEM privileges.
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 confidenceThe Checkmk Windows Agent's data directory has incorrect permissions that allow a local unprivileged user to modify files in that directory. This can be exploited to achieve local privilege escalation to SYSTEM by replacing agent files or configurations that are executed with elevated privileges.
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<= 2.0.0= 2.1.0= 2.2.0= 2.3.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Checkmk Windows Agent is installedCheck for the presence of Checkmk agent files in Program Files or ProgramData directories, or look for the Checkmk service in Windows Services (services.msc)Affected if The Checkmk Windows Agent service or files are present on the system
-
Determine the installed Checkmk agent versionCheck the version of the installed Checkmk Windows Agent by examining the binary properties of the main agent executable (typically at C:\Program Files (x86)\checkmk\service\cmk.exe or in the ProgramData directory), or run 'cmk --version' if availableAffected if The installed version is 2.0.0 or lower, or between 2.1.0 and 2.1.0p44, or between 2.2.0 and 2.2.0p28, or between 2.3.0 and 2.3.0p7 (check against the known affected ranges)
-
Identify the Checkmk data directory locationCheck the default data directory path, typically C:\ProgramData\checkmk\agent\ or C:\Program Files (x86)\checkmk\agent\, or inspect the service configuration to find the configured data directoryAffected if A Checkmk data directory exists on the system
-
Inspect permissions on the Checkmk data directoryRight-click the data directory in Windows Explorer, go to Properties > Security tab, or run 'icacls <directory>' from an elevated command prompt to view the ACL entries. Check if Users or other unprivileged groups have Write or Modify permissionsAffected if Unprivileged users (such as Users group or standard users) have Write, Modify, or Full Control permissions to the data directory, allowing them to replace agent files or configurations
The system is affected if the Checkmk Windows Agent is installed with a version in the affected range AND the data directory grants write permissions to unprivileged users, allowing file replacement that could lead to privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Checkmk versions 2.3.0p8, 2.2.0p29, or 2.1.0p45 or later. For end-of-life versions (2.0.0p39 and below), upgrade to a supported release branch.
Upgrade to Checkmk 2.3.0p8 (or later), 2.2.0p29 (or later), 2.1.0p45 (or later), or to a currently supported version if on 2.0.0p39 or earlier
- 1. Identify the current Checkmk version by checking the Checkmk web interface or running 'cmk --version' on the command line
- 2. Based on the current version, determine the target patch release: For 2.3.0 series, upgrade to 2.3.0p8 or later; For 2.2.0 series, upgrade to 2.2.0p29 or later; For 2.1.0 series, upgrade to 2.1.0p45 or later; For 2.0.0 and earlier, these versions are End-of-Life (EOL) and require a major version upgrade to a supported release
- 3. Before upgrading, back up the Checkmk configuration and database to prevent data loss
- 4. Download the appropriate patch version from the official Checkmk download site (checkmk.com)
- 5. Follow Checkmk's standard upgrade procedure for the target version, which typically involves running the setup script or using the package manager
- 6. After upgrade, verify the Windows Agent data directory permissions have been corrected - the directory should no longer allow unprivileged users to modify files that could lead to privilege escalation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-28827 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-28827 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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