Rocket.Chat Mobile up to 4.5.0 E2EE Password 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.
4.4$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Rocket.Chat Mobile up to 4.5.0. Affected by this vulnerability is an unknown functionality of the component E2EE Password Handler. Performing a manipulation results in entropy. This vulnerability is reported as CVE-2024-42027. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Rocket.Chat Mobile up to 4.5.0. This affects some unknown functionality of the component E2EE Password Handler. The manipulation with an unknown input leads to a entropy vulnerability. CWE is classifying the issue as CWE-331. The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others. This is going to have an impact on confidentiality. The summary by CVE is:

The E2EE password entropy generated by Rocket.Chat Mobile prior to version 4.5.1 is insufficient, allowing attackers to crack it if they have the appropriate time and resources.

The advisory is shared at hackerone.com. This vulnerability is uniquely identified as CVE-2024-42027 since 07/27/2024. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Additional levels of successful authentication are required for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.

Upgrading to version 4.5.1 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.4
VulDB Meta Temp Score: 4.4

VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.7
CNA Vector (hackerone): 🔍

CVSSv2info

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

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

Exploitinginfo

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

Physical: No
Local: No
Remote: Yes

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: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Mobile 4.5.1

Timelineinfo

07/27/2024 🔍
10/07/2024 +72 days 🔍
10/07/2024 +0 days 🔍
10/07/2024 +0 days 🔍

Sourcesinfo

Advisory: hackerone.com
Status: Confirmed

CVE: CVE-2024-42027 (🔍)
GCVE (CVE): GCVE-0-2024-42027
GCVE (VulDB): GCVE-100-279477

Entryinfo

Created: 10/07/2024 15:33
Changes: 10/07/2024 15:33 (66)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

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!