Threats affecting pkg:golang/github.com/neuvector/neuvector

The NeuVector admission webhook silently excludes containers from policy evaluation when their image path matches one of three hardcoded service mesh sidecar images. Since the image path is entirely controlled by the workload author, any user capable of deploying workloads can evade admission deny rules simply by naming their image path after one of these sidecar images.

Authorised users of outside applications behind the same corporate identity provider (IdP), for example, a wiki, a ticketing system, an expenses tool, or anything they legitimately hold an account on can log into their system via SAML SSO. The IdP issues an assertion to them. If that assertion is presented to NeuVector, NeuVector accepts it because the only thing distinguishing "an assertion for NeuVector" from "an assertion for the wiki" is the element, and the `NotInAudience` warning that reports the mismatch is never read.

The NeuVector JWT verifier accepts noncanonical Base64URL encodings of the same RSA signature field. An attacker holding a valid JWT that has not expired, but was logged out of NeuVector, can continue using the non-expired token with equivalent spelling of the RSA signature field until the token validity expires.

For users authenticated through SAML or OpenID Connect (OIDC), this vulnerability can result in one user receiving another user's authenticated session when multiple SSO login attempts occur concurrently

NeuVector versions prior to 5.4.7 contain a hard-coded cryptographic key embedded in the binary, used to encrypt sensitive configuration data. This static key approach poses a security risk as the key is fixed and potentially exposed. The issue is resolved in version 5.4.7 and later, where NeuVector uses a dynamically generated encryption key stored securely as a Kubernetes secret, improving key management and security. There is no workaround; users must upgrade to a fixed version.

NeuVector Enforcer contains a critical vulnerability where environment variables CLUSTER_RPC_PORT and CLUSTER_LAN_PORT are used unsafely to construct shell commands executed via popen without sanitization. This allows command injection and buffer overflow within the enforcer container. The issue is fixed in versions 5.3.5, 5.4.7, and later. No workaround exists; users must upgrade promptly.