CVE-2024-0670
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 · uneditedPrivilege escalation in windows agent plugin in Checkmk before 2.2.0p23, 2.1.0p40 and 2.0.0 (EOL) allows local user to escalate 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 confidenceA privilege escalation vulnerability exists in the Checkmk Windows agent plugin. Local users can exploit this to gain elevated privileges on systems where the Checkmk Windows agent is installed. The vulnerability affects versions prior to 2.2.0p23 and 2.1.0p40.
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.1.0= 2.2.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.
-
Verify Checkmk Windows agent is installedOpen Programs and Features (appwiz.cpl) or check the Windows services list for a service named 'Checkmk Agent' or similarAffected if No Checkmk Windows agent is found in installed programs or services, the system is not affected
-
Locate the Checkmk agent executableCheck common installation paths such as C:\Program Files\Checkmk\ or C:\Program Files (x86)\Checkmk\ for the agent executable (typically named check_mk_agent.exe or similar)Affected if No Checkmk agent executable is found in expected locations
-
Retrieve the installed versionRight-click the agent executable, select Properties, and check the Details tab for Product Version, or run 'Get-ItemProperty -Path "<path_to_executable>" | Select-Object ProductVersion' in PowerShellAffected if The displayed version falls within these affected ranges: 2.0.x (any version < 2.1.0), 2.1.0 (without p40 patch), or 2.2.0 (without p23 patch)
-
Confirm the agent plugin component is activeCheck if the Checkmk agent service is running and examine the agent configuration for enabled plugins (typically in the \plugins\ subdirectory of the agent installation)Affected if The Checkmk Windows agent service is running with plugins enabled on an affected version
A system is affected if the Checkmk Windows agent is installed and the installed version is 2.0.x, 2.1.0, or 2.2.0 (prior to the p40 and p23 patches respectively).
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 · scoped2.1.0
Upgrade Checkmk Windows agent to version 2.2.0p23, 2.1.0p40, or later. For EOL version 2.0.0, migrate to a supported version.
2.2.0p23 (or 2.1.0p40 for 2.1.x branches)
- Upgrade Checkmk to version 2.2.0p23 or later (recommended)
- If running 2.1.x, upgrade to 2.1.0p40 or later
- If running 2.0.x, note that 2.0.0 is End-of-Life; plan migration to 2.2.x
- Download the updated Checkmk Windows agent from the vendor's official source
- Uninstall the current Windows agent and install the updated version
- Verify the installation and ensure no unauthorized DLL files exist in the agent directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-0670 — 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-0670 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