Bludit 2.0 Token weak prng

Summaryinfo

A vulnerability was found in Bludit 2.0. It has been rated as problematic. The impacted element is an unknown function of the component Token Handler. The manipulation leads to weak prng. This vulnerability is uniquely identified as CVE-2024-24554. No exploit exists.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Bludit 2.0. This issue affects an unknown function of the component Token Handler. The manipulation with an unknown input leads to a weak prng vulnerability. Using CWE to declare the problem leads to CWE-338. The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong. Impacted is confidentiality. The summary by CVE is:

Bludit uses predictable methods in combination with the MD5 hashing algorithm to generate sensitive tokens such as the API token and the user token. This allows attackers to authenticate against the Bludit API.

The weakness was disclosed by Andreas Pfefferle. It is possible to read the advisory at redguard.ch. The identification of this vulnerability is CVE-2024-24554 since 01/25/2024. The exploitation is known to be difficult. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600.001 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• Bludit

Version

• 2.0

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion