Submariner-operator: broker serviceaccount secret (token + ca) logged in full at trace verbosity
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in the submariner-operator component. The `submariner-k8s-broker-cluster` Role, which is assigned to joined clusters, possesses excessive permissions. This allows a compromised cluster to alter network configurations, specifically by overwriting other clusters' endpoint information. Consequently, an attacker can redirect inter-cluster tunnel traffic, enabling a Man-in-the-Middle (MITM) attack across the entire cluster mesh.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- rhacm2/submariner-addon-rhel9
Version range not reported
- rhacm2/submariner-addon-rhel9
Version range not reported
- rhacm2/submariner-addon-rhel9
Version range not reported
- rhacm2/submariner-addon-rhel9
Version range not reported
- rhacm2/submariner-addon-rhel9
Version range not reported
- rhacm2/subctl-rhel9
Version range not reported
- rhacm2/submariner-rhel9-operator
Version range not reported
- rhacm2/subctl-rhel9
Version range not reported
- rhacm2/submariner-rhel9-operator
Version range not reported
- rhacm2/submariner-addon-rhel9
Version range not reported
- rhacm2/submariner-operator-bundle
Version range not reported