GHSA-qqj3-g7mx-5p4w NeuVector telemetry sender is vulnerable to MITM and DoS

• Go github.com/neuvector/neuvector: >= 0.0.0-20230727023453-1c4957d53911, < 0.0.0-20251020133207-084a437033b4 → fixed in 0.0.0-20251020133207-084a437033b4

Impact This vulnerability affects NeuVector deployments only when the `Report anonymous cluster data option` is enabled. When this option is enabled, NeuVector sends anonymous telemetry data to the telemetry server at `https://upgrades.neuvector-upgrade-responder.livestock.rancher.io`. In affected versions, NeuVector does not enforce TLS certificate verification when transmitting anonymous cluster data to the telemetry server. As a result, the communication channel is susceptible to man-in-the-middle (MITM) attacks, where an attacker could intercept or modify the transmitted data. Additionally, NeuVector loads the response of the telemetry server is loaded into memory without size limitation, which makes it vulnerable to a Denial of Service(DoS) attack. The patched version includes the following security improvements: • NeuVector now verifies the telemetry server’s `TLS certificate chain` and `hostname` during the handshake process. This ensures that all telemetry communications occur over a trusted and verified channel. • NeuVector limits the telemetry server’s response to `256 bytes`, mitigating the risk of memory exhaustion and DoS attacks. These security enhancements are enabled by default and require no user action. Patches Patched versions include release v5.4.7 and above. Workarounds If you cannot update to a patched version, you can temporarily disable the Report anonymous cluster data, which is enabled by default in NeuVector. To change this setting, go to Settings → Configuration → Report anonymous cluster data in the NeuVector UI. Disabling this option prevents NeuVector from sending telemetry data to the telemetry server, which helps mitigate this vulnerability. References If you have any questions or comments about this advisory: • Reach out to the SUSE Rancher Security team for security related inquiries. • Open an issue in the NeuVector repository. • Verify with our support matrix and product support lifecycle.