PT-2025-54685 · Go · Github.Com/Neuvector/Neuvector
Publicado
2025-12-12
·
Atualizado
2025-12-12
CVSS v3.1
8.8
Alta
| Vetor | AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Impact
NeuVector supports login authentication through OpenID Connect. However, the TLS verification (which verifies the remote server's authenticity and integrity) for OpenID Connect is not enforced by default. As a result this may expose the system to man-in-the-middle (MITM) attacks.
Starting from version 5.4.0, NeuVector supports TLS verification for following connection types:
- Registry Connections
- Auth Server Connections (SAML, LDAP and OIDC)
- Webhook Connections
By default, TLS verification remains disabled, and its configuration is located under Settings > Configuration in the NeuVector UI.
In the patched version, the new NeuVector deployment enables TLS verification by default.
For rolling upgrades, NeuVector does not automatically change this setting to prevent disruptions.
Note: When "TLS verification" is enabled, it affects all connections to:
- Registry servers
- Auth servers (SAML, LDAP and OIDC)
- Webhook servers
Patches
Patched versions include release v5.4.8 and above.
Workarounds
To manually enable TLS verification:
- Open the NeuVector UI.
- Navigate to Settings > Configuration.
- In the TLS Self-Signed Certificate Configuration section, select Enable TLS verification.
- (Optional) Upload or paste the TLS self-signed certificate.
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.
Correção
Improper Certificate Validation
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Enumeração de Fraquezas
Identificadores relacionados
Produtos afetados
Github.Com/Neuvector/Neuvector