CVE-2014-5968
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 iGolf - Golf GPS (aka com.igolf) application 20 for Android does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
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 iGolf Golf GPS Android application version 20 fails to validate X.509 certificates when establishing SSL/TLS connections. This allows man-in-the-middle attackers to intercept traffic by presenting forged certificates, enabling them to capture sensitive data transmitted between the app and backend servers.
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= 20CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/AC:M/Au:N/C:P/I:P/A:P
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 if iGolf Golf GPS app is installedOn Android devices, check installed applications for 'iGolf Golf GPS' or 'Igolf Igolf Golf Gps' - use device management tools, MDM inventory, or manually check Settings > AppsAffected if The app is present on any Android device in the environment
-
Determine the installed app versionCheck the app version in the Android app details (Settings > Apps > iGolf Golf GPS > Version) or query via ADB: 'adb shell dumpsys package com.igolf.gps' or similar package nameAffected if The installed version is exactly version 20
-
Verify network traffic capabilityDetermine if the app has network permissions and communicates with backend servers - check AndroidManifest.xml for INTERNET permission and analyze network traffic if possibleAffected if The app has network capability and transmits data to remote servers
-
Check for SSL/TLS traffic interceptionIf the app is in use, attempt to probe its SSL/TLS implementation through a proxy or observe certificate validation behavior - the vulnerability exists if the app accepts self-signed or invalid certificates without warningAffected if The app accepts invalid or untrusted X.509 certificates during SSL/TLS connections
You are affected if iGolf Golf GPS version 20 is installed on any Android device in your environment and that device uses the app to transmit data over network connections.
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.
From vendor dataImplement proper SSL certificate validation in the application by using trusted certificate stores, configuring SSLContext with a valid TrustManager, and/or implementing certificate pinning for critical endpoints.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5968 — 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-2014-5968 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