CVE-2024-47130
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 allows unauthenticated attackers to remotely update the local public keys used for P2P and group messages. It is advised to update your app 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 · high confidenceThe goTenna Pro App lacks authentication checks on its public key update mechanism, allowing any remote attacker to replace the local public keys used for P2P and group message encryption. This key substitution could enable man-in-the-middle attacks by allowing attackers to inject their own keys into the keyring, undermining the app's end-to-end encryption.
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
- 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 the installed goTenna Pro App versionAccess the app's settings menu, typically found under Settings > About or Settings > App Info. The version number will be displayed alongside the app name.Affected if The installed version is 1.6.1 or lower, or any version 2.x below 2.0.3.
-
Verify if P2P messaging is configured or activeOpen the goTenna Pro App and navigate to the messaging section. Look for P2P direct message functionality or peer-to-peer connection settings.Affected if P2P messaging features are available or have been used on the affected version.
-
Verify if group messaging is configured or activeOpen the goTenna Pro App and navigate to the group messaging section. Look for group creation or group chat features.Affected if Group messaging features are available or have been used on the affected version.
-
Confirm the app's public key update behaviorAttempt to locate the keyring or public key management interface within the app. Check if there are any indicators of key exchange or if keys can be viewed or exported.Affected if The app allows viewing or managing public keys for encryption, which would be vulnerable to substitution on affected versions.
A user is affected if the goTenna Pro App version is 1.6.1 or lower, or between 2.0.0 and 2.0.2, and P2P or group messaging features are used.
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 the goTenna Pro App to the latest version which contains proper authentication for key update operations and enhanced encryption protocols. Until updated, avoid using P2P and group messaging features.
2.0.3 or later (current release)
- Update goTenna Pro App to version 2.0.3 or later
- Verify the application was updated successfully
- Confirm the app is running the latest available release
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-47130 — 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-47130 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