CVE-2024-28825
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 · uneditedImproper restriction of excessive authentication attempts on some authentication methods in Checkmk before 2.3.0b5 (beta), 2.2.0p26, 2.1.0p43, and in Checkmk 2.0.0 (EOL) facilitates password brute-forcing.
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 confidenceCheckmk before versions 2.3.0b5, 2.2.0p26, and 2.1.0p43 fails to properly restrict excessive authentication attempts on certain authentication methods, allowing remote attackers to conduct unlimited password brute-forcing attacks against the login interface.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed Checkmk versionRun 'cmk --version' or check the Checkmk web interface footer for the version numberAffected if The installed version is 2.0.0 or lower, or exactly 2.1.0, 2.2.0, or 2.3.0 (before the patched releases)
-
Determine if web login interface is exposedAccess the Checkmk login page at your instance URL and confirm the login form is reachable without rate limitingAffected if The login interface is accessible externally or internally without any authentication attempt limits enforced
-
Identify authentication methods in useReview Checkmk authentication settings in 'Setup > General > Authentication' or check the etc/checkmk directory for auth configurationAffected if Basic authentication or other non-rate-limited methods are enabled for user login
-
Check for rate limiting configurationSearch for rate limit, login attempt limits, or account lockout settings in Checkmk configuration files or the web interface under security settingsAffected if No rate limiting, login attempt throttling, or account lockout mechanism is configured or active
-
Verify if password brute-forcing is possibleAttempt multiple failed login attempts (in a test environment) to confirm whether the system blocks or throttles repeated authentication failuresAffected if The system allows unlimited failed login attempts without any lockout or delay
You are affected if your Checkmk version falls within the affected ranges (2.0.0 and below, or exactly 2.1.0, 2.2.0, or 2.3.0) and the login interface permits unlimited authentication attempts without rate limiting or account lockout.
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 the patched versions (2.3.0b5+, 2.2.0p26+, 2.1.0p43+) which implement proper rate limiting or account lockout mechanisms. As a compensating control, implement network-level IP blocking or use a WAF to limit authentication attempts.
2.3.0 (stable) or latest 2.x release; for specific patches: 2.2.0p26, 2.1.0p43
- 1. Identify your current Checkmk version using 'cmk --version' or the web UI
- 2. For Checkmk 2.3.x: Upgrade to 2.3.0 or later stable release that includes the fix
- 3. For Checkmk 2.2.x: Upgrade to version 2.2.0p26 or later
- 4. For Checkmk 2.1.x: Upgrade to version 2.1.0p43 or later
- 5. For Checkmk 2.0.0: This version is End-of-Life (EOL) with no patch available; migrate to a supported version (2.1.0p43+, 2.2.0p26+, or 2.3.0+)
- 6. After upgrade, verify the web interface is accessible and services are running using 'cmk -D'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-28825 — 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-28825 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