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.
References
| Link | Resource |
|---|---|
| https://www.wired.com/story/how-the-signal-knock-off-app-telemessage-got-hacked-in-20-minutes/ | Press/Media Coverage |
Configurations
History
22 Oct 2025, 15:14
| Type | Values Removed | Values Added |
|---|---|---|
| First Time |
Smarsh telemessage
Smarsh |
|
| References | () https://www.wired.com/story/how-the-signal-knock-off-app-telemessage-got-hacked-in-20-minutes/ - Press/Media Coverage | |
| CPE | cpe:2.3:a:smarsh:telemessage:*:*:*:*:*:*:*:* |
01 Jul 2025, 20:15
| Type | Values Removed | Values Added |
|---|---|---|
| Summary |
|
|
| Summary | (en) 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. |
28 May 2025, 17:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-05-28 17:15
Updated : 2025-10-22 15:14
NVD link : CVE-2025-48925
Mitre link : CVE-2025-48925
CVE.ORG link : CVE-2025-48925
JSON object : View
Products Affected
smarsh
- telemessage
CWE
CWE-836
Use of Password Hash Instead of Password for Authentication
