CVE-2024-41722
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 · uneditedIn the goTenna Pro ATAK Plugin there is a vulnerability that makes it possible to inject any custom message with any GID and Callsign using a software defined radio in existing goTenna mesh networks. This vulnerability can be exploited if the device is being used in an unencrypted environment or if the cryptography has already been compromised. It is advised to use encryption shared 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 lacks proper message authentication when operating in unencrypted mode, allowing an attacker with a software defined radio to inject arbitrary messages with any GID and Callsign into the mesh network. Exploitation requires either an unencrypted environment or a pre-compromised cryptography layer.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 software versionLocate the installed Gotenna Pro ATAK Plugin version in the application settings, about menu, or system package information. For Android ATAK, check Apps > Gotenna Plugin > Version information.Affected if The installed version is below 2.0.7 (e.g., 2.0.6, 2.0.5, etc.)
-
Check encryption status in plugin settingsOpen the Gotenna ATAK Plugin settings menu and locate the encryption or security configuration options. Verify whether encryption is currently enabled or disabled for mesh communications.Affected if Encryption is disabled or set to 'unencrypted' mode for message transmission
-
Verify cryptography layer integrityReview the encryption key configuration. Confirm that keys were exchanged via secure methods (local QR code) rather than over-the-air or unsecured channels. Check for any signs of key compromise in the key management interface.Affected if Encryption keys were exchanged via insecure methods, or the cryptography layer shows signs of tampering or compromise
-
Confirm mesh node configurationExamine the Gotenna device or plugin node settings to determine if the device is operating in a mode that accepts unauthenticated messages from other nodes.Affected if The device is configured to accept messages without cryptographic verification from unknown GIDs
You are affected if your Gotenna Pro ATAK Plugin version is below 2.0.7 AND unencrypted mode is enabled, or if your encryption layer has been compromised, allowing unauthenticated message injection into your mesh network.
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
Enable encryption and use local QR code key exchange for all operations instead of unencrypted mode to prevent message injection attacks.
2.0.7
- 1. Check the current version of goTenna Pro ATAK Plugin installed on the device
- 2. Navigate to the device's app store (Google Play Store or Apple App Store)
- 3. Search for goTenna Pro ATAK Plugin
- 4. Update to version 2.0.7 or later
- 5. After updating, configure encryption using the local QR code sharing method for higher security operations as recommended by the vendor
- 6. Verify the updated version is reflected in the application settings or about section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41722 — 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-41722 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