Vulnerability Details : CVE-2023-22359
User enumeration in Checkmk <=2.2.0p4 allows an authenticated attacker to enumerate usernames.
Products affected by CVE-2023-22359
- cpe:2.3:a:checkmk:checkmk:2.2.0:i1:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:-:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b1:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b2:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b3:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b4:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b5:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b6:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b7:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:b8:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:p1:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:p2:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:p3:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.2.0:p4:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2023-22359
0.05%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 18 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2023-22359
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
4.3
|
MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
2.8
|
1.4
|
NIST | |
4.3
|
MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
2.8
|
1.4
|
Checkmk GmbH |
CWE ids for CVE-2023-22359
-
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.Assigned by: security@checkmk.com (Secondary)
-
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.Assigned by: security@checkmk.com (Secondary)
References for CVE-2023-22359
-
https://checkmk.com/werk/15890
user: read permissions are now checked in the request schema before delete/edit/create userVendor Advisory
Jump to