service vulnerabilities
5 known vulnerabilities in service from TeleMessage. 3 are rated high or critical, and 2 have been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
The TeleMessage service through 2025-05-05 implements authentication through a long-lived…
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.
- 4.0 Medium severity
TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere Exploited
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.
- 5.3 Medium severity
TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Exploited
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.
- 7.5 High severity
service: Authentication Bypass Using an Alternate Path or Channel
The admin panel in the TeleMessage service through 2025-05-05 allows attackers to discover usernames, e-mail addresses, passwords, and telephone numbers.
- 7.5 High severity
service: Use of Password Hash Instead of Password for Authentication
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.