CVE-2024-47124
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 encrypt callsigns in messages. It is recommended to not use sensitive information in callsigns when using this and previous versions of the app and update your app to the current app version which uses AES-256 encryption for callsigns in encrypted operation.
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 transmits callsigns in plaintext without encryption, allowing eavesdroppers to capture user identifiers in messages. The vulnerability is resolved in newer versions that implement AES-256 encryption for callsigns in encrypted operation mode.
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
- 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.
-
Determine the installed goTenna Pro app versionOpen the goTenna Pro app and navigate to Settings > About, or check the app version in your device's app store or installed applications listAffected if The installed version is 1.6.1 or lower, or falls below version 2.0.3
-
Verify the current operation modeIn the goTenna Pro app, check the radio settings or connection mode to determine if the device is operating in encrypted mode or plaintext modeAffected if The app is set to use unencrypted or plaintext operation mode
-
Inspect callsign transmission settingsNavigate to the app's callsign or user ID settings and check if AES-256 encryption for callsigns is explicitly enabled or availableAffected if AES-256 encryption for callsigns is not enabled or not available in the current version
You are affected if your goTenna Pro app version is 1.6.1 or lower, below 2.0.3, or if you are operating without AES-256 encrypted callsign protection.
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
Update to the latest app version that implements AES-256 encryption for callsigns; avoid using sensitive or personal information in callsigns until the update is applied.
2.0.3 or later (current version with AES-256 encryption for callsigns)
- Check the current installed version of the goTenna Pro App on your device
- Navigate to the Apple App Store (iOS) or Google Play Store (Android) on your device
- Search for "goTenna Pro" or locate it in your installed apps
- Tap Update to install the latest version (version 2.0.3 or higher)
- After updating, verify the app version shows 2.0.3 or later in the app settings or store listing
- Ensure you are using encrypted operation mode within the app for callsign transmission
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47124 — 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-47124 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