CVE-2014-6739
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 Well-Being Connect Mobile (aka com.healthways.wellbeinggo) application 2.9 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 Well-Being Connect Mobile Android application version 2.9 fails to validate X.509 certificates during SSL/TLS connections, allowing man-in-the-middle attackers to intercept traffic by presenting fraudulent certificates and spoof legitimate servers to harvest sensitive user data.
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= 2.9CVSS 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.
-
Confirm installed application versionUse Android package manager commands (adb shell pm list packages) to find packages containing 'wellbeing' or 'healthways', then check the version using adb shell dumpsys package or through device settings under Apps > Well-Being Connect > Version.Affected if Version 2.9 of Healthways Well-Being Connect Mobile is installed
-
Locate network traffic code in the APKDecompile the APK using apktool or similar tools, then locate source files handling HTTP/HTTPS connections (look for classes using HttpURLConnection, HttpsURLConnection, or network libraries).Affected if The app contains code for making network requests to external servers
-
Inspect SSL/TLS certificate validation implementationIn the decompiled code, search for TrustManager, HostnameVerifier, or custom socket factory implementations. Examine whether the app properly validates certificate chains, or uses implementations that accept all certificates (for example, custom TrustManager that overrides checkServerTrusted without proper validation).Affected if Code contains custom TrustManager or HostnameVerifier that bypasses or weakens certificate validation, or accepts all certificates unconditionally
-
Test with invalid certificate using MITM proxySet up a proxy (such as Burp Suite or mitmproxy) with an invalid or self-signed certificate and attempt to intercept traffic from the app. If the app connects successfully without certificate warnings, validation is not properly enforced.Affected if The app accepts invalid or self-signed certificates and completes SSL/TLS connections to the proxy
The environment is affected if version 2.9 of the Well-Being Connect Mobile app is installed AND the app fails to properly validate X.509 certificate chains during SSL/TLS 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/TLS certificate validation including chain-of-trust verification and hostname validation; consider adding certificate pinning for critical endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6739 — 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-6739 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