Bludit: Use of Password Hash With Insufficient Computational Effort
CVE-2024-24553 is a high-severity use of password hash with insufficient computational effort vulnerability in Bludit, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Bludit versions: 2.0; 2.0 through 3.15.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Bludit you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on redguard.ch for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 5.9 | Medium | CNA (ncsc.ch) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
Bludit uses the SHA-1 hashing algorithm to compute password hashes. Thus, attackers could determine cleartext passwords with brute-force attacks due to the inherent speed of SHA-1. In addition, the salt that is computed by Bludit is generated with a non-cryptographically secure function.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: 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.
How developers prevent this class of flaw
- When using industry-approved techniques, use them correctly. Don't cut corners by skipping resource-intensive steps (CWE-325). These steps are often essential for preventing common attacks.
More Use of Password Hash With Insufficient Computational Effort vulnerabilities (CWE-916)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- redguard.ch/blog/2024/06/20/security-advisory-bludit/Third Party Advisory
Other vulnerabilities in Bludit
- 7.1 High severity
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.2 High severity
- 8.8 High severity
Recent Use of Password Hash With Insufficient Computational Effort vulnerabilities
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.1 High severity
Spotted an error? Tell us.