TeleMessage Service up to 2025-05-05 Password weak hash
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in TeleMessage Service up to 2025-05-05. Affected by this issue is some unknown functionality of the component Password Handler. This manipulation causes weak hash. This vulnerability is registered as CVE-2025-48931. The attack needs to be launched locally. Furthermore, an exploit is available. This product operates as a managed service, which prevents users from maintaining vulnerability countermeasures themselves.
Details
A vulnerability classified as problematic was found in TeleMessage Service up to 2025-05-05. Affected by this vulnerability is an unknown functionality of the component Password Handler. The manipulation with an unknown input leads to a weak hash vulnerability. The CWE definition for the vulnerability is CWE-328. The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack). As an impact it is known to affect confidentiality. The summary by CVE is:
The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack possibilities (including rainbow tables) with low computational effort.
The advisory is shared at wired.com. This vulnerability is known as CVE-2025-48931 since 05/28/2025. The exploitation appears to be difficult. An attack has to be approached locally. Technical details are unknown but an exploit is available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
It is declared as attacked.
This product is available as a managed service. Users are not able to maintain vulnerability countermeasures themselves.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Managed Service
- yes
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.7VulDB Meta Temp Score: 3.7
VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
NVD Vector: 🔍
CNA Base Score: 3.2
CNA Vector (MITRE): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Weak hashCWE: CWE-328 / CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Attacked
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Status: 🔍0-Day Time: 🔍
Timeline
05/28/2025 🔍05/28/2025 🔍
05/28/2025 🔍
10/03/2025 🔍
Sources
Advisory: wired.comStatus: Confirmed
CVE: CVE-2025-48931 (🔍)
GCVE (CVE): GCVE-0-2025-48931
GCVE (VulDB): GCVE-100-310465
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/28/2025 20:35Updated: 10/03/2025 20:00
Changes: 05/28/2025 20:35 (64), 10/03/2025 20:00 (12)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.