- What is the severity of CVE-2024-24553?
- CVE-2024-24553 has been scored as a medium severity vulnerability.
- How to fix CVE-2024-24553?
- To fix CVE-2024-24553: 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.
- Is CVE-2024-24553 being actively exploited in the wild?
- As for now, there are no information to confirm that CVE-2024-24553 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
- What software or system is affected by CVE-2024-24553?
- CVE-2024-24553 affects Bludit Bludit.