Submariner-operator: pprof debug endpoint enabled by default on 0.0.0.0:8082 without authentication
- 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: partial
Summary
A flaw was found in the Submariner operator. The Submariner Custom Resource (CR), used for configuring network connectivity, stores the IPsec pre-shared key (PSK) in an unencrypted format. This key, which is critical for securing communication between Kubernetes clusters, can be accessed by unauthorized parties. Such access enables an attacker to passively decrypt network traffic flowing between any two clusters in the mesh, resulting in sensitive information disclosure.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- 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/submariner-addon-rhel9
Version range not reported
- rhacm2/subctl-rhel9
Version range not reported
- rhacm2/submariner-rhel9-operator
Version range not reported
- rhacm2/submariner-operator-bundle
Version range not reported