CVE-2024-47121
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe goTenna Pro App uses a weak password for sharing encryption keys via the key broadcast method. If the broadcasted encryption key is captured over RF, and password is cracked via brute force attack, it is possible to decrypt it and use it to decrypt all future and past messages sent via encrypted broadcast with that particular key. This only applies when the key is broadcasted over RF. This is an optional feature, so it is recommended to use local QR encryption key sharing for additional security on this and previous versions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe goTenna Pro App uses a weak password for sharing encryption keys via RF broadcast. An attacker who captures the broadcasted encryption key over RF and brute-forces the weak password can decrypt the key and use it to decrypt all past and future messages sent via encrypted broadcast with that key.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm goTenna Pro App installationIdentify if the goTenna Pro App is installed on your device. This is the pro/enterprise version of the goTenna application, distinct from the consumer goTenna app.Affected if The goTenna Pro App is present on the device
-
Check installed version numberLocate the version information for the installed goTenna Pro App (typically found in app settings, about section, or device app management). Compare it against the affected range: any version prior to 2.0.3.Affected if Installed version is less than 2.0.3
-
Verify RF key broadcast is enabledAccess the goTenna Pro App settings and examine the encryption or key sharing configuration. Look for options related to RF key broadcast, key sharing over radio, or remote key distribution. Check if this feature is toggled on or active.Affected if RF key broadcast feature is enabled in the application settings
-
Determine if RF broadcast was used for key sharingReview the application's key management history, logs, or past key sharing operations. Identify whether any encryption keys were distributed using the RF broadcast method rather than local QR code transfer.Affected if Any encryption keys were shared via RF broadcast method
You are affected only if you have goTenna Pro App version below 2.0.3 AND the RF key broadcast feature is enabled AND you have used it to share encryption keys; using QR code-based key sharing with a vulnerable version does not expose you to this specific flaw.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.0.3
Disable the RF key broadcast feature and use local QR code-based encryption key sharing instead, as recommended by the vendor.
2.0.3
- Upgrade goTenna Pro App to version 2.0.3 or later to obtain the fixed release
- As an additional security measure, use local QR encryption key sharing instead of RF key broadcast method when possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-47121 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data