CVE-2014-6714
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 WebMD (aka com.webmd.android) application 3.5 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 WebMD Android application version 3.5 fails to verify X.509 certificates from SSL servers during HTTPS connections. This certificate validation failure allows man-in-the-middle attackers to present fraudulent certificates and intercept or modify 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= 3.5CVSS 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.
-
Check if WebMD app is installedOn Android device: Go to Settings > Apps > find WebMD, or run 'adb shell pm list packages | grep webmd' to list packages. Note the installed version shown in the app details.Affected if WebMD application version 3.5 is installed on the device
-
Verify the exact installed version numberIn Settings > Apps > WebMD, check the Version field under App Info. Alternatively, run 'adb shell dumpsys package com.webmd.android | grep versionName' to get the precise version string.Affected if The version displayed is exactly 3.5
-
Confirm the app makes network requestsCheck if the WebMD app has been used or has permissions for network access. Review app permissions in Settings > Apps > WebMD > Permissions, looking for INTERNET permission.Affected if The app has INTERNET permission and has been used to connect to WebMD services
-
Check for SSL certificate validation implementationThis requires static analysis of the APK. Extract APK from device or obtain it from an APK repository. Use a decompiler (e.g., jadx) to examine the source code for SSL/TLS handling. Search for implementations of TrustManager, X509TrustManager, or hostnameVerifier that may be accepting all certificates.Affected if Code analysis reveals TrustManager or hostnameVerifier implementations that bypass certificate validation (e.g., empty implementations or returning true for all certificates)
The environment is affected if WebMD Android application version 3.5 is installed and the app makes HTTPS connections without proper X.509 certificate validation, which can be confirmed through static code analysis of the APK.
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 in the Android app, including X.509 chain verification and hostname validation. Consider adding certificate pinning for sensitive endpoints to prevent MITM attacks.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6714 — 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-6714 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