Submariner-operator: pprof debug endpoint enabled by default on 0.0.0.0:8082 without authentication

Overview

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.

Affected

• rhacm2/submariner-addon-rhel9 (all versions)
• rhacm2/submariner-addon-rhel9 (all versions)
• rhacm2/submariner-addon-rhel9 (all versions)
• rhacm2/submariner-addon-rhel9 (all versions)
• rhacm2/submariner-addon-rhel9 (all versions)
• rhacm2/subctl-rhel9 (all versions)
• rhacm2/submariner-rhel9-operator (all versions)
• rhacm2/submariner-addon-rhel9 (all versions)
• rhacm2/subctl-rhel9 (all versions)
• rhacm2/submariner-rhel9-operator (all versions)
• rhacm2/submariner-operator-bundle (all versions)

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

Workarounds

To mitigate the risk of IPsec pre-shared key (PSK) disclosure, implement strict Kubernetes Role-Based Access Control (RBAC) policies to limit access to Submariner Custom Resources. Ensure that only authorized administrators and systems are granted permissions to view submariner Custom Resources within their namespaces. Additionally, exercise caution when collecting and storing diagnostic data, such as must-gather bundles, and when managing GitOps repositories, as these may inadvertently expose the cleartext PSK.