Broadcast decryption via co-stored keys and static IV
Published Sep 26, 2024 · Updated Oct 17, 2024
Insecure key storage in goTenna Pro App 1.61 and earlier allows physically proximate attackers to decrypt broadcast communications. The app stores encryption keys on the end-user device beside a static initialization vector, enabling recovery of the keys from a compromised device. Physical access and control of the end-user device are required; recovered keys expose the confidentiality of broadcasts encrypted with those keys.
Summary
What happened
Insecure key storage in goTenna Pro App 1.61 and earlier allows physically proximate attackers to decrypt broadcast communications. The app stores encryption keys on the end-user device beside a static initialization vector, enabling recovery of the keys from a compromised device. Physical access and control of the end-user device are required; recovered keys expose the confidentiality of broadcasts encrypted with those keys.
The record
- CVE
- CVE-2024-47122
- Published
- Sep 26, 2024
- Updated
- Oct 17, 2024
- Vendor
- goTenna
- Product
- goTenna Pro
- Classifications
- CWE-922, T1552.001
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2024CVE publishedPublication date reported by the CVE source.
- Oct 17, 2024Record 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?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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