In-cluster service impersonation via overbroad CA bundle
Published Jul 30, 2021 · Updated Aug 3, 2024
Improper certificate validation in Red Hat OpenShift Container Platform before 4.8 allows attackers to impersonate trusted in-cluster services. The injected service-ca.crt trust bundle includes ingress and other internal CAs instead of only the service-serving signer. Upgraded 4.8 clusters can retain the legacy bundle; exploitation requires control of an included CA and can expose or alter trusted traffic.
Summary
What happened
Improper certificate validation in Red Hat OpenShift Container Platform before 4.8 allows attackers to impersonate trusted in-cluster services. The injected service-ca.crt trust bundle includes ingress and other internal CAs instead of only the service-serving signer. Upgraded 4.8 clusters can retain the legacy bundle; exploitation requires control of an included CA and can expose or alter trusted traffic.
The record
- CVE
- CVE-2021-3636
- Published
- Jul 30, 2021
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Container Platform
- Classifications
- CWE-295, T1557
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2021CVE 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=openshift 4.8
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.
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