CVE-2024-47126
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 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 broadcast of an encryption key, so it is advised to share the key with local QR code for higher security operations.
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 · moderate confidenceThe goTenna Pro App uses a non-cryptographically secure random number generator when creating passwords for sharing cryptographic keys. This weakness allows attackers to more easily brute force these passwords if they capture the broadcasted encryption key over RF, as the entropy of the generated passwords is significantly reduced.
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<= 1.6.1< 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Verify goTenna Pro is installedLocate the goTenna Pro application on your system or device using your system's application list, package manager, or file systemAffected if goTenna Pro application is present on the system
-
Identify installed versionAccess the application's About, Settings, or version information panel to retrieve the exact version number installedAffected if The version number cannot be determined or is not visible
-
Compare version to affected rangesTake the installed version and compare it against the affected ranges: versions <= 1.6.1 or versions < 2.0.3Affected if Your installed version falls within <= 1.6.1 or < 2.0.3 (for example, 1.5.0, 1.6.1, 2.0.0, 2.0.2 would all be affected)
-
Determine if RF key sharing is usedCheck whether the application is configured to use RF (radio frequency) broadcasting for cryptographic key exchange rather than local methods like QR code sharingAffected if RF broadcasting is enabled or commonly used for key exchange in your workflow
You are affected if your goTenna Pro version is 1.6.1 or lower, or between 2.0.0 and 2.0.2 inclusive, AND you use RF broadcasting for key exchange.
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
Replace the insecure random function with a cryptographically secure alternative like SecureRandom, and for high-security operations use local QR code sharing instead of RF broadcasting for key exchange.
goTenna Pro >= 2.0.3
- Verify current goTenna Pro app version installed on device
- Upgrade goTenna Pro to version 2.0.3 or later
- After upgrade, for highest security operations, use local QR code sharing method instead of RF broadcast for encryption keys
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47126 — 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-47126 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