CVE-2024-28828
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 · uneditedCross-Site request forgery in Checkmk < 2.3.0p8, < 2.2.0p29, < 2.1.0p45, and <= 2.0.0p39 (EOL) could lead to 1-click compromize of the site.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in Checkmk monitoring platform. Attackers can craft malicious links or pages that trick authenticated users into performing unintended administrative actions on the Checkmk site, potentially leading to full compromise with a single click.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Determine Checkmk installed versionCheck the Checkmk version via the web interface (Help > About) or by running 'cmk --version' or 'check_mk --version' on the command lineAffected if The displayed version is 2.0.0, 2.1.0, 2.2.0, or 2.3.0 (or any point release within these branches such as 2.3.0p1-p7, 2.2.0p1-p28, 2.1.0p1-p44)
-
Confirm the exact version numberNote the full version string including any patch level (for example: 2.3.0p5, 2.2.0p15, 2.1.0p30)Affected if The version shows 2.3.0p7 or earlier, 2.2.0p28 or earlier, or 2.1.0p44 or earlier - these are all vulnerable
-
Identify if the instance handles authenticated user sessionsReview whether the Checkmk site has active users and is used by administrators who perform actions like creating hosts, configuring rules, or managing notificationsAffected if The Checkmk instance has authenticated users with administrative privileges, and the CSRF vulnerability can be exploited through malicious links tricking these users
You are affected if your Checkmk version is 2.3.0p7 or earlier, 2.2.0p28 or earlier, 2.1.0p44 or earlier, or 2.0.0p39 and below - especially if the instance has authenticated administrative users.
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 Checkmk to version 2.3.0p8, 2.2.0p29, 2.1.0p45 or later. Version 2.0.0p39 and below are End-of-Life and require upgrading to a supported release branch.
2.3.0p8 (or later), 2.2.0p29 (or later), or 2.1.0p45 (or later) - note: 2.0.0 is EOL
- Identify your current Checkmk version by checking the installation
- If running 2.3.0 series: upgrade to version 2.3.0p8 or later
- If running 2.2.0 series: upgrade to version 2.2.0p29 or later
- If running 2.1.0 series: upgrade to version 2.1.0p45 or later
- If running 2.0.0 series: note that 2.0.0 is End-of-Life (EOL); migrate to a supported version branch (2.1.0, 2.2.0, or 2.3.0)
- After upgrade, verify the site is functioning normally
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28828 — 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-28828 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