RT-Thread up to 5.0.2 drivers/misc/rt_random.c entropy

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.6$0-$5k0.00

Summaryinfo

A vulnerability was found in RT-Thread up to 5.0.2. It has been classified as problematic. This affects an unknown function of the file drivers/misc/rt_random.c. Performing a manipulation results in entropy. This vulnerability was named CVE-2024-25389. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, was found in RT-Thread up to 5.0.2. This affects an unknown code block of the file drivers/misc/rt_random.c. The manipulation with an unknown input leads to a entropy vulnerability. CWE is classifying the issue as CWE-332. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. This is going to have an impact on confidentiality. The summary by CVE is:

RT-Thread through 5.0.2 generates random numbers with a weak algorithm of "seed = 214013L * seed + 2531011L; return (seed >> 16) & 0x7FFF;" in calc_random in drivers/misc/rt_random.c.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-25389 since 02/07/2024. The exploitability is told to be difficult. Technical details of the vulnerability are known, but there is no available exploit. 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

Version

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.6
VulDB Meta Temp Score: 2.6

VulDB Base Score: 2.6
VulDB Temp Score: 2.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Entropy
CWE: CWE-332 / CWE-331 / CWE-330
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

02/07/2024 🔍
03/27/2024 +49 days 🔍
03/27/2024 +0 days 🔍
04/17/2025 +386 days 🔍

Sourcesinfo

Product: github.com

Advisory: 8283
Status: Confirmed

CVE: CVE-2024-25389 (🔍)
GCVE (CVE): GCVE-0-2024-25389
GCVE (VulDB): GCVE-100-258123

Entryinfo

Created: 03/27/2024 07:35
Updated: 04/17/2025 07:40
Changes: 03/27/2024 07:35 (52), 04/17/2025 07:40 (2)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!