CVE-2024-45723
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 ATAK Plugin 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 ATAK Plugin uses a weak random number generator instead of SecureRandom when generating passwords for sharing cryptographic keys. This makes passwords vulnerable to brute force attacks if the broadcasted encryption key is captured over RF (radio frequency). The vulnerability only affects the optional RF broadcast feature for key sharing.
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.7CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/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.
-
Identify goTenna Pro ATAK Plugin installationLocate the goTenna application on the device. On Android, check installed applications for 'goTenna' or 'gotenna Pro ATAK Plugin'. On iOS, check the application list for the goTenna app.Affected if The goTenna application is installed on the device.
-
Determine installed goTenna versionOpen the goTenna application settings or app info screen to view the current software version. Compare this version number against the affected range of versions prior to 2.0.7.Affected if The installed version is lower than 2.0.7.
-
Verify RF broadcast key sharing is enabledAccess the goTenna application settings and inspect the key exchange or key sharing configuration options. Look for settings related to RF broadcast, over-the-air key sharing, or password-based key exchange methods.Affected if The RF broadcast feature for key sharing is enabled or has been used.
-
Confirm key sharing method usedReview recent key exchange logs or operation history within the goTenna ATAK Plugin to identify if passwords were broadcast via radio frequency for cryptographic key sharing.Affected if RF broadcast was used as the key sharing method rather than local methods like QR code exchange.
You are affected if the goTenna Pro ATAK Plugin is installed with a version lower than 2.0.7 and the RF broadcast feature has been used for sharing cryptographic keys.
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.7
Replace the weak random number generator with SecureRandom (cryptographically secure RNG) for password generation, or use local QR code sharing instead of RF broadcasting for key exchange in high-security operations.
2.0.7
- Obtain goTenna Pro ATAK Plugin version 2.0.7 or later from the official vendor
- Upgrade the goTenna Pro ATAK Plugin to version 2.0.7
- After upgrading, regenerate any previously broadcast encryption keys since they may have been generated with weak randomness
- For high-security operations, share encryption keys via local QR code instead of RF broadcast
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45723 — 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-45723 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