dbcve.org
GotennaApplication

CVE-2024-43108

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-26
Fix available
A fix is available. Upgrade to 2.0.7 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
The goTenna Pro ATAK Plugin uses AES CTR type encryption for short, encrypted messages without any additional integrity checking mechanisms. This leaves messages malleable to an attacker that can access the message. It is advised to continue to use encryption in the plugin and update to the current release for enhanced encryption protocols.

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 confidence

The goTenna Pro ATAK Plugin uses AES CTR (Counter) mode for message encryption without any integrity verification mechanism (such as MAC, HMAC, or authenticated encryption). This allows attackers with message access to perform bit-flipping attacks, modifying encrypted content without detection due to the lack of authentication tags.

MitigationUpdate to the current release of the goTenna Pro ATAK Plugin which includes enhanced encryption protocols with built-in integrity checking. If current version must be used, implement additional message authentication (e.g., HMAC) before transmitting.

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
GotennaApplication
Affected:< 2.0.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify goTenna Pro ATAK Plugin version
    Open ATAK and navigate to the plugin management section. Find goTenna Pro ATAK Plugin in the list of installed plugins and note the version number displayed.
    Affected if The displayed version is less than 2.0.7 (e.g., 2.0.6, 2.0.5, 1.x.x)
  2. Verify encryption is in use
    Check the goTenna Pro plugin settings or communication configuration. Look for encryption mode settings, typically found under message encryption, link encryption, or security settings within the plugin configuration menu.
    Affected if AES CTR mode encryption is enabled or selected as the encryption method
  3. Confirm integrity verification is absent
    Inspect the plugin security or encryption settings for any message authentication configuration. Look for options labeled MAC, HMAC, message integrity, authentication tag, or authenticated encryption (GCM, CCM). Check if these are disabled, missing, or not present.
    Affected if No MAC, HMAC, or authenticated encryption mode (such as GCM) is configured or available in the plugin settings
  4. Check for bit-flipping vulnerability exposure
    If possible, capture and inspect outgoing messages from the plugin using a network analyzer or debug tool. Examine the encrypted payload for the absence of an authentication tag or integrity checksum at the end of the ciphertext.
    Affected if Encrypted messages contain no detectable authentication tag or integrity check value

You are affected if the installed goTenna Pro ATAK Plugin version is below 2.0.7 AND AES CTR encryption is in use without any MAC, HMAC, or authenticated encryption providing integrity verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.0.7 or later
Fixed in 2.0.7
Interim mitigation

Update to the current release of the goTenna Pro ATAK Plugin which includes enhanced encryption protocols with built-in integrity checking. If current version must be used, implement additional message authentication (e.g., HMAC) before transmitting.

Recommended fix High confidence

2.0.7

  1. Obtain the goTenna Pro ATAK Plugin version 2.0.7 or later from the official goTenna distribution channel
  2. Uninstall the current version of the goTenna Pro ATAK Plugin from your ATAK instance
  3. Install version 2.0.7 of the goTenna Pro ATAK Plugin
  4. Verify the installed version matches 2.0.7 or later in the plugin settings
  5. Test message encryption functionality to confirm the enhanced encryption protocols are operational
Caveat Enhanced encryption protocols in 2.0.7 may affect interoperability with older plugin versions; ensure all communication partners upgrade to maintain compatibility

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gotenna Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43108 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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