Vulnerabilities (CVE)

Filtered by vendor Smarsh Subscribe
Filtered by product Telemessage
Total 8 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2025-48925 1 Smarsh 1 Telemessage 2025-10-22 N/A 4.3 MEDIUM
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.
CVE-2025-48926 1 Smarsh 1 Telemessage 2025-10-22 N/A 4.3 MEDIUM
The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail addresses, passwords, and telephone numbers.
CVE-2025-48929 1 Smarsh 1 Telemessage 2025-10-22 N/A 4.0 MEDIUM
The TeleMessage service through 2025-05-05 implements authentication through a long-lived credential (e.g., not a token with a short expiration time) that can be reused at a later date if discovered by an adversary.
CVE-2025-47730 1 Smarsh 1 Telemessage 2025-10-22 N/A 4.8 MEDIUM
The TeleMessage archiving backend through 2025-05-05 accepts API calls (to request an authentication token) from the TM SGNL (aka Archive Signal) app with the credentials of logfile for the user and enRR8UVVywXYbFkqU#QDPRkO for the password.
CVE-2025-48930 1 Smarsh 1 Telemessage 2025-10-22 N/A 2.8 LOW
The TeleMessage service through 2025-05-05 stores certain cleartext information in memory, even though memory content may be accessible to an adversary through various avenues.
CVE-2025-48928 1 Smarsh 1 Telemessage 2025-10-21 N/A 4.0 MEDIUM
The TeleMessage service through 2025-05-05 is based on a JSP application in which the heap content is roughly equivalent to a "core dump" in which a password previously sent over HTTP would be included in this dump, as exploited in the wild in May 2025.
CVE-2025-48927 1 Smarsh 1 Telemessage 2025-10-21 N/A 5.3 MEDIUM
The TeleMessage service through 2025-05-05 configures Spring Boot Actuator with an exposed heap dump endpoint at a /heapdump URI, as exploited in the wild in May 2025.
CVE-2025-48931 1 Smarsh 1 Telemessage 2025-10-03 N/A 3.2 LOW
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.