Second-factor bypass via uncounted authentication failures
Published Jun 10, 2024 · Updated Aug 2, 2024
Improper authentication-attempt restriction in Checkmk 2.3 before 2.3.0p6 allows remote attackers to bypass two-factor protection. Two-factor failures were omitted from the failed-login counter, so repeated incorrect second factors never triggered the account lockout applied to other login failures. The attack requires reaching a two-factor challenge for a user account and can expose data protected by that account.
Summary
What happened
Improper authentication-attempt restriction in Checkmk 2.3 before 2.3.0p6 allows remote attackers to bypass two-factor protection. Two-factor failures were omitted from the failed-login counter, so repeated incorrect second factors never triggered the account lockout applied to other login failures. The attack requires reaching a two-factor challenge for a user account and can expose data protected by that account.
The record
- CVE
- CVE-2024-28833
- Published
- Jun 10, 2024
- Updated
- Aug 2, 2024
- Vendor
- Checkmk GmbH
- Product
- Checkmk
- Classifications
- CWE-307, T1110
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.3.0 <2.3.0p6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo