Lighthouse: lighthouse: arbitrary namespace injection via attacker-controlled broker label
- 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 Lighthouse. A remote attacker, by compromising a spoke cluster, can exploit a vulnerability where the destination namespace for resource injection is derived from an attacker-controlled label or annotation on the broker object. This allows the attacker to inject unauthorized EndpointSlices and ServiceImports into any namespace on peer clusters, including critical system namespaces like kube-system and openshift-*. This could lead to privilege escalation or other forms of system compromise within the cluster.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- rhacm2/lighthouse-agent-rhel9
Version range not reported
- rhacm2/lighthouse-coredns-rhel9
Version range not reported
- rhacm2/subctl-rhel9
Version range not reported
- rhacm2/submariner-rhel9-operator
Version range not reported
- rhacm2/lighthouse-agent-rhel9
Version range not reported
- rhacm2/lighthouse-coredns-rhel9
Version range not reported
- rhacm2/subctl-rhel9
Version range not reported
- rhacm2/submariner-rhel9-operator
Version range not reported