← Back

Smarsh

smarsh

8 CVEs • 1 product

Products (1)

Click to collapse
Toggle
Telemessage
telemessage

CVEs (8)

CVE
VENDORS
PRODUCTS
UPDATED
PUBLISHED
CVSS
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
5.5 MEDIUM· v3
N/A· v2
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.
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
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.
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
9.8 CRITICAL· v3
N/A· v2
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.
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
4.0 MEDIUM· v3
N/A· v2
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 e...Show more
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.Show less
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
5.3 MEDIUM· v3
N/A· v2
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.
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
7.5 HIGH· v3
N/A· v2
The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail addresses, passwords, and telephone numbers.
1Smarsh
1Telemessage
Jun 17, 2026
May 28, 2025
N/A· v4
7.5 HIGH· v3
N/A· v2
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.
1Smarsh
1Telemessage
Jun 17, 2026
May 8, 2025
N/A· v4
7.5 HIGH· v3
N/A· v2
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#QDP...Show more
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.Show less