Message decryption via brute-forced broadcast key password
Published Sep 26, 2024 · Updated May 2, 2025
Weak password requirements in goTenna Pro 1.61 and earlier allow physically proximate attackers to decrypt broadcasts after RF key capture. The key-broadcast method protects a shared encryption key with a weak password, enabling offline brute-force recovery from a captured radio transmission. Exploitation requires the optional RF key-broadcast feature; recovery exposes past and future encrypted broadcasts using that key.
Summary
What happened
Weak password requirements in goTenna Pro 1.61 and earlier allow physically proximate attackers to decrypt broadcasts after RF key capture. The key-broadcast method protects a shared encryption key with a weak password, enabling offline brute-force recovery from a captured radio transmission. Exploitation requires the optional RF key-broadcast feature; recovery exposes past and future encrypted broadcasts using that key.
The record
- CVE
- CVE-2024-47121
- Published
- Sep 26, 2024
- Updated
- May 2, 2025
- Vendor
- goTenna
- Product
- goTenna Pro
- Classifications
- CWE-521, T1040, T1110.002
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2024CVE publishedPublication date reported by the CVE source.
- May 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.61
What conditions does exploitation require?
What is affected?
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