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.
Advisories
Source ID Title
EUVD EUVD EUVD-2024-21971 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.
Fixes

Solution

To address this vulnerability, it is imperative that the Bludit development team transitions to a more secure and intentionally slow hashing algorithm, such as bcrypt or Argon2, for password storage. These algorithms introduce the necessary computational overhead to resist brute-force attacks effectively. In addition, it is advised that appropriate cost factors are used. Furthermore, the generation of password salts should be revamped to employ a cryptographically secure method. The current approach, utilizing the `Text::randomText function`, should be replaced with a robust random number generator provided by the operating system or a dedicated cryptographic library. This change ensures the creation of unpredictable and secure salts, enhancing the overall resilience of the password storage mechanism.


Workaround

No workaround given by the vendor.

History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: NCSC.ch

Published:

Updated: 2024-08-01T23:19:52.892Z

Reserved: 2024-01-25T14:02:00.526Z

Link: CVE-2024-24553

cve-icon Vulnrichment

Updated: 2024-08-01T23:19:52.892Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-06-24T07:15:15.063

Modified: 2024-11-21T08:59:24.207

Link: CVE-2024-24553

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2025-07-12T23:05:43Z