Cluster namespace creation via insufficient access controls
Published Jun 27, 2023 · Updated Nov 1, 2024
Improper access control in IBM Robotic Process Automation allows local users to create namespaces in its OpenShift cluster. IBM has not published the misconfigured control or the operation that accepts unauthorized namespace creation in affected 21.0.1 through 21.0.7.3 and 23.0.0 through 23.0.3 deployments. The attack requires local cluster access and changes cluster integrity, with no disclosed ability to read data or interrupt service.
Summary
What happened
Improper access control in IBM Robotic Process Automation allows local users to create namespaces in its OpenShift cluster. IBM has not published the misconfigured control or the operation that accepts unauthorized namespace creation in affected 21.0.1 through 21.0.7.3 and 23.0.0 through 23.0.3 deployments. The attack requires local cluster access and changes cluster integrity, with no disclosed ability to read data or interrupt service.
The record
- CVE
- CVE-2023-23468
- Published
- Jun 27, 2023
- Updated
- Nov 1, 2024
- Vendor
- IBM
- Product
- IBM Robotic Process Automation
- Classifications
- CWE-284
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2023CVE publishedPublication date reported by the CVE source.
- Nov 1, 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=21.0.1 <=21.0.7.3
- Affected versionversion=23.0.0 <=23.0.3
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