NeuVector telemetry sender is vulnerable to MITM and DoS
- 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
- Fix
- Fixed in 5.3.5, 5.4.7, 0.0.0-20251020133207-084a437033b4
- 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: yes
- Technical impact: partial
Summary
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. 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
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- https://github.com/neuvector/neuvector
From 5.3.0 · fixed in 5.3.5; From 5.4.0 · fixed in 5.4.7; From 0.0.0-20230727023453-1c4957d53911 · fixed in 0.0.0-20251020133207-084a437033b4
- github.com/neuvector/neuvectorGo
All versions
- github.com/neuvector/neuvectorGo
From 0.0.0-20230727023453-1c4957d53911 · fixed in 0.0.0-20251020133207-084a437033b4