SMS service abuse via hardcoded verification token
Published May 1, 2025 · Updated May 1, 2025
Hard-coded credentials in goTenna v1 app 5.5.3 and firmware 0.25.5 allow local users to abuse the SMS service through a reused token. The app embeds a verification token used to authorize SMS requests through a goTenna server instead of obtaining a per-user secret. Local access to the app is required to recover the token, after which the shared credential permits unauthorized SMS requests and service interruption.
Summary
What happened
Hard-coded credentials in goTenna v1 app 5.5.3 and firmware 0.25.5 allow local users to abuse the SMS service through a reused token. The app embeds a verification token used to authorize SMS requests through a goTenna server instead of obtaining a per-user secret. Local access to the app is required to recover the token, after which the shared credential permits unauthorized SMS requests and service interruption.
The record
- CVE
- CVE-2025-32889
- Published
- May 1, 2025
- Updated
- May 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-798, T1552.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 1, 2025CVE publishedPublication date reported by the CVE source.
- May 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo