CVE-2024-8606
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 · uneditedBypass of two factor authentication in RestAPI in Checkmk < 2.3.0p16 and < 2.2.0p34 allows authenticated users to bypass two factor authentication
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 confidenceTwo-factor authentication bypass in Checkmk's REST API allows authenticated users to circumvent 2FA protections. This vulnerability affects Checkmk versions prior to 2.3.0p16 and 2.2.0p34, enabling attackers with valid credentials to access the API without completing 2FA verification.
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.3.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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify Checkmk installation versionRun the command 'cmk --version' or 'omd version' on the Checkmk server to determine the installed version numberAffected if The version shown is 2.3.0 prior to patch 16, or 2.2.0 prior to patch 34
-
Verify REST API is enabledCheck the Checkmk web interface under 'Setup > General > API' or inspect the API configuration file in the Checkmk etc directory to confirm the REST API is activeAffected if The REST API is enabled and the installed version falls within the affected ranges
-
Confirm 2FA is configured for the accountNavigate to the user profile in Checkmk under 'User > 2-Factor Authentication' or check if any 2FA provider (such as TOTP, email, or SMS) is configured for the userAffected if Two-factor authentication is enabled for the user account accessing the REST API
-
Compare version against affected rangesReview the full version string (including patch level) against the affected versions: 2.3.0 through 2.3.0p15, and 2.2.0 through 2.2.0p33Affected if The installed version is any release between 2.3.0 and 2.3.0p15 inclusive, or between 2.2.0 and 2.2.0p33 inclusive
A user is affected if they are running Checkmk versions 2.3.0 through 2.3.0p15 or 2.2.0 through 2.2.0p33 with the REST API enabled and 2FA configured for API access.
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.0p16 or 2.2.0p34 or later to remediate this vulnerability.
Checkmk 2.3.0p16 or 2.2.0p34 (depending on your current major version)
- Upgrade Checkmk 2.3.0 to version 2.3.0p16 or later
- Upgrade Checkmk 2.2.0 to version 2.2.0p34 or later
- After upgrade, verify that 2FA authentication is enforced for RestAPI users by testing authentication with and without 2FA
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-8606 — 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-8606 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