NeuVector telemetry sender is vulnerable to MITM and DoS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| SUSE | neuvector | unaffected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Suse | Neuvector | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-qqj3-g7mx-5p4w | NeuVector telemetry sender is vulnerable to MITM and DoS |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.198% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Suse
Suse neuvector |
|
| Vendors & Products |
Suse
Suse neuvector |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 | |
| Title | NeuVector telemetry sender is vulnerable to MITM and DoS | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV3_1
|