TeleMessage Service up to 2025-05-05 password hash instead of password for authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in TeleMessage Service up to 2025-05-05. This impacts an unknown function. The manipulation leads to use of password hash instead of password for authentication. This vulnerability is documented as CVE-2025-48925. The attack can be initiated remotely. Additionally, an exploit exists. This product is a managed service. It is not possible for users to maintain vulnerability countermeasures themselves.
Details
A vulnerability was found in TeleMessage Service up to 2025-05-05 and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a use of password hash instead of password for authentication vulnerability. Using CWE to declare the problem leads to CWE-836. The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store. Impacted is integrity. The summary by CVE is:
The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential, as exploited in the wild in May 2025.
It is possible to read the advisory at wired.com. The identification of this vulnerability is CVE-2025-48925 since 05/28/2025. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are unknown but an exploit is available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/23/2025). The attack technique deployed by this issue is T1550.002 according to MITRE ATT&CK.
It is declared as attacked.
This product is available as a managed service. Users are not able to maintain vulnerability countermeasures themselves.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-16211). Statistical analysis made it clear that VulDB provides the best quality for 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: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 4.3
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: Use of password hash instead of password for authenticationCWE: CWE-836
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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/23/2025 🔍
Sources
Advisory: wired.comStatus: Confirmed
CVE: CVE-2025-48925 (🔍)
GCVE (CVE): GCVE-0-2025-48925
GCVE (VulDB): GCVE-100-310451
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/28/2025 20:29Updated: 10/23/2025 04:40
Changes: 05/28/2025 20:29 (60), 05/28/2025 20:30 (3), 07/01/2025 23:05 (1), 07/02/2025 08:25 (1), 10/23/2025 04:40 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.