Cross-pod port access via malformed NetworkPolicy nesting
Published Aug 22, 2022 · Updated Aug 3, 2024
Improper access control in Red Hat OpenShift Service Mesh 2.0.5.1 allows attackers controlling any pod to reach unintended ports. The servicemesh-operator emits ingress rules with the port field at the wrong YAML nesting level, so Kubernetes does not restrict ingress to the intended named port. Control of any cluster pod permits direct interaction with otherwise blocked ports on affected mesh control-plane and observability resources.
Summary
What happened
Improper access control in Red Hat OpenShift Service Mesh 2.0.5.1 allows attackers controlling any pod to reach unintended ports. The servicemesh-operator emits ingress rules with the port field at the wrong YAML nesting level, so Kubernetes does not restrict ingress to the intended named port. Control of any cluster pod permits direct interaction with otherwise blocked ports on affected mesh control-plane and observability resources.
The record
- CVE
- CVE-2021-3586
- Published
- Aug 22, 2022
- Updated
- Aug 3, 2024
- Vendor
- Red Hat
- Product
- Red Hat OpenShift Service Mesh
- Classifications
- CWE-1188
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 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=Affects v2.0.5.1, Fixed in v2.0.5.2.
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