CVE-2024-47125
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 authenticate public keys which allows an unauthenticated attacker to manipulate 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 · moderate confidenceThe goTenna Pro App fails to authenticate public keys during cryptographic operations, allowing an unauthenticated attacker to intercept and manipulate messages. This public key authentication bypass enables man-in-the-middle attacks on the communication channel.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Locate goTenna Pro App on your deviceOpen your device settings (iOS Settings app or Android Settings), navigate to the applications or apps section, and search for 'goTenna Pro' in the installed apps listAffected if The app is not found, meaning goTenna Pro is not installed (not affected)
-
Find the installed version numberIn the app details screen (typically Settings > Apps > goTenna Pro > App info or similar), locate the 'Version' or 'Version number' field which displays the current software versionAffected if Cannot determine version - further investigation needed
-
Compare version against vulnerable range <= 1.6.1Check if the installed version number is 1.6.1 or any earlier version (e.g., 1.6.0, 1.5.x, 1.0.x)Affected if Installed version is 1.6.1 or lower - affected by CVE-2024-47125
-
Compare version against vulnerable range < 2.0.3If the version is 2.0.x, check if it is below 2.0.3 (e.g., 2.0.2, 2.0.1, 2.0.0)Affected if Installed version is 2.0.2 or lower in the 2.0.x line - affected by CVE-2024-47125
The device is affected if the goTenna Pro App is installed and the version is either 1.6.1 or lower, or any version from 2.0.0 to 2.0.2.
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 includes enhanced encryption protocols with proper public key authentication. Verify all deployed instances are running the patched version.
Update to goTenna Pro version 2.0.3 or later (current release)
- Open the goTenna Pro application on your device
- Navigate to the application settings or about section
- Check the current installed version number
- Access the official app store (Apple App Store or Google Play Store) or goTenna's official website
- Search for goTenna Pro and check for available updates
- If an update is available, download and install version 2.0.3 or the current latest release
- After installation, verify the new version number in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47125 — 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-47125 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