Skip to content

NeuVector has an insecure password storage vulnerable to rainbow attack

Moderate severity GitHub Reviewed Published Aug 26, 2025 in neuvector/neuvector • Updated Aug 28, 2025

Package

gomod github.com/neuvector/neuvector (Go)

Affected versions

>= 5.0.0, < 5.4.6

Patched versions

5.4.6

Description

Impact

NeuVector stores user passwords and API keys using a simple, unsalted hash. This method is vulnerable to rainbow table attack (offline attack where hashes of known passwords are precomputed).

NeuVector generates a cryptographically secure, random 16-character salt and uses it with the PBKDF2 algorithm to create the hash value for the following actions:

  • Creating a user
  • Updating a user’s password
  • Creating an API key

Note: After upgrading to NeuVector 5.4.6, users must log in again so that NeuVector can regenerate the password hash. For API keys, you must send at least one request per API key to regenerate its hash value.

Patches

This issue is fixed in NeuVector version 5.4.6 and later.

Workarounds

There is no workaround. Upgrade to a patched version of NeuVector as soon as possible.

References

If you have any questions or comments about this advisory:

References

@BinX-Suse BinX-Suse published to neuvector/neuvector Aug 26, 2025
Published to the GitHub Advisory Database Aug 28, 2025
Reviewed Aug 28, 2025
Last updated Aug 28, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS score

Weaknesses

Use of a One-Way Hash without a Salt

The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input. Learn more on MITRE.

Use of Password Hash With Insufficient Computational Effort

The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive. Learn more on MITRE.

CVE ID

CVE-2025-53884

GHSA ID

GHSA-8ff6-pc43-jwv3

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.