Authenticated username enumeration via missing read-permission checks
Published Jun 26, 2023 · Updated Aug 28, 2024
User enumeration in the REST API of Checkmk 2.2.0 through 2.2.0p4 allows remote authenticated users to discover valid usernames. The user_config request schemas for create, edit, and delete operations fail to check user-read permission before processing a supplied username. Any authenticated account can probe these endpoints and learn which usernames exist, exposing account identifiers without gaining modification rights.
Summary
What happened
User enumeration in the REST API of Checkmk 2.2.0 through 2.2.0p4 allows remote authenticated users to discover valid usernames. The user_config request schemas for create, edit, and delete operations fail to check user-read permission before processing a supplied username. Any authenticated account can probe these endpoints and learn which usernames exist, exposing account identifiers without gaining modification rights.
The record
- CVE
- CVE-2023-22359
- Published
- Jun 26, 2023
- Updated
- Aug 28, 2024
- Vendor
- Checkmk GmbH
- Product
- Checkmk
- Classifications
- CWE-203, CAPEC-575, T1087
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2023CVE publishedPublication date reported by the CVE source.
- Aug 28, 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.0p4
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