Two-factor authentication bypass via incomplete session validation
Published Sep 23, 2024 · Updated Sep 23, 2024
Incorrect authorization in the Checkmk REST API allows remote authenticated users to bypass required two-factor authentication. The REST API accepts a partially authenticated session without verifying every required factor in 2.2.0 before 2.2.0p34 and 2.3.0 before 2.3.0p16. A valid first-factor login is required, after which protected API operations become available without completion of the configured second factor.
Summary
What happened
Incorrect authorization in the Checkmk REST API allows remote authenticated users to bypass required two-factor authentication. The REST API accepts a partially authenticated session without verifying every required factor in 2.2.0 before 2.2.0p34 and 2.3.0 before 2.3.0p16. A valid first-factor login is required, after which protected API operations become available without completion of the configured second factor.
The record
- CVE
- CVE-2024-8606
- Published
- Sep 23, 2024
- Updated
- Sep 23, 2024
- Vendor
- Checkmk GmbH
- Product
- Checkmk
- Classifications
- CWE-863, CAPEC-115, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 23, 2024CVE publishedPublication date reported by the CVE source.
- Sep 23, 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.2.0 <2.2.0p34
- Affected versionversion=2.3.0 <2.3.0p16
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