NeuVector Enforcer is vulnerable to Command Injection and Buffer overflow
SUSE neuvector
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/neuvector/neuvector Go |
|
|
SUSE neuvector
| Product | Affected | Fixed in |
|---|---|---|
| github.com/neuvector/neuvector Go |
|
|
A vulnerability was identified in NeuVector, where the enforcer used environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT to generate a command to be executed via popen, without first sanitising their values.
The entry process of the enforcer container is the monitor process. When the enforcer container stops, the monitor process checks whether the consul subprocess has exited. To perform this check, the monitor process uses the popen function to execute a shell command that determines whether the ports used by the consul subprocess are still active.
The values of environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT are used directly to compose shell commands via popen without validation or sanitization. This behavior could allow a malicious user to inject malicious commands through these variables within the enforcer container.
From the CVE record · suse
The NeuVector enforcer monitor uses unsanitized CLUSTER_RPC_PORT and CLUSTER_LAN_PORT environment variables to build a shell command executed through popen. A malicious user who can set these variables within the enforcer container could inject commands when the container stops and the monitor checks whether the consul subprocess has exited.
Teams running SUSE NeuVector with Go package github.com/neuvector/neuvector versions >=5.3.0 <5.3.5, >=5.4.0 <5.4.7, or >=0.0.0-20230727023453-1c4957d53911 <0.0.0-20251020133207-084a437033b4 should check their deployments.