The goTenna Pro App allows unauthenticated attackers to remotely update the local public keys used for P2P and group messages. It is advised to update your app to the current release for enhanced encryption protocols.
Product
goTenna pro app vulnerabilities
6 published CVES affecting goTenna pro app, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 6
- Critical
- 0
- High
- 3
- Medium
- 3
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest goTenna pro app CVEs
Newest publication first
-
HighCVSS 8.7 EPSS 0.22%
-
MediumCVSS 5.3 EPSS 0.14%
The goTenna Pro App does not inject extra characters into broadcasted frames to obfuscate the length of messages. This makes it possible to tell the length of the payload regardless of the encryption used.
-
MediumCVSS 5.3 EPSS 0.13%
The goTenna Pro App encryption key name is always sent unencrypted when the key is shared over RF through a broadcast message. It is advised to share the encryption key via local QR for higher security operations.
-
MediumCVSS 6.0 EPSS 0.11%
In the goTenna Pro App there is a vulnerability that makes it possible to inject any custom message with any GID and Callsign using a software defined radio in existing goTenna mesh networks. This vulnerability can be exploited if the device is being used in an unencrypted enviro...
-
CVE-2024-47126 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in goTenna Pro
PublishedHighCVSS 7.1 EPSS 0.24%The goTenna Pro App does not use SecureRandom when generating passwords for sharing cryptographic keys. The random function in use makes it easier for attackers to brute force this password if the broadcasted encryption key is captured over RF. This only applies to the optional b...
-
CVE-2024-47125 Improper Restriction of Communication Channel to Intended Endpoints in goTenna Pro
PublishedHighCVSS 7.6 EPSS 0.14%The goTenna Pro App does not authenticate public keys which allows an unauthenticated attacker to manipulate messages. It is advised to update your app to the current release for enhanced encryption protocols.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.