| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Open Cluster Management. This affects an unknown function of the component Worker Node Handler. The manipulation leads to privilege chaining. This vulnerability is referenced as CVE-2023-2250. Remote exploitation of the attack is possible. No exploit is available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Open Cluster Management (version now known) and classified as problematic. This issue affects some unknown processing of the component Worker Node Handler. The manipulation with an unknown input leads to a privilege chaining vulnerability. Using CWE to declare the problem leads to CWE-268. Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination. Impacted is confidentiality. The summary by CVE is:
A flaw was found in the Open Cluster Management (OCM) when a user have access to the worker nodes which has the cluster-manager-registration-controller or cluster-manager deployments. A malicious user can take advantage of this and bind the cluster-admin to any service account or using the service account to list all secrets for all kubernetes namespaces, leading into a cluster-level privilege escalation.
The weakness was published 04/25/2023. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-2250 since 04/24/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-33758). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.6VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Privilege chainingCWE: CWE-268 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
04/24/2023 🔍04/25/2023 🔍
04/25/2023 🔍
12/17/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2023-2250 (🔍)
GCVE (CVE): GCVE-0-2023-2250
GCVE (VulDB): GCVE-100-227345
EUVD: 🔍
Entry
Created: 04/25/2023 07:08Updated: 12/17/2025 22:57
Changes: 04/25/2023 07:08 (37), 05/18/2023 15:29 (11), 12/17/2025 22:57 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.