Clusterwide privilege escalation via exposed service account token
Published Jun 21, 2022 · Updated Aug 3, 2024
Privilege escalation in Red Hat AMQ Broker Operator 7.9.4 and earlier allows remote authenticated users to gain clusterwide edit rights. The OperatorHub installation exposes a build service-account token through namespace-readable secrets and assigns that account excessive clusterwide permissions. A compromised low-privilege namespace account or insider can use the token to read or modify resources across the OpenShift cluster.
Summary
What happened
Privilege escalation in Red Hat AMQ Broker Operator 7.9.4 and earlier allows remote authenticated users to gain clusterwide edit rights. The OperatorHub installation exposes a build service-account token through namespace-readable secrets and assigns that account excessive clusterwide permissions. A compromised low-privilege namespace account or insider can use the token to read or modify resources across the OpenShift cluster.
The record
- CVE
- CVE-2022-1833
- Published
- Jun 21, 2022
- Updated
- Aug 3, 2024
- Vendor
- 389 Directory Server
- Product
- Red Hat AMQ Broker
- Classifications
- CWE-276, T1552.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 21, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=AMQ Broker Operator 7.9.4 and prior
What conditions does exploitation require?
What is affected?
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