CVE-2014-6005
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 Survey.com Mobile (aka com.survey.android) application 3.2.16 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 Survey.com Mobile Android application version 3.2.16 fails to validate X.509 certificates during SSL/TLS connections, enabling man-in-the-middle attackers to intercept sensitive data by presenting fraudulent certificates.
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.2.16CVSS 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 Survey.com Mobile is installedOn Android devices, go to Settings > Apps > Downloaded, or use adb command: 'adb shell pm list packages' to list all installed packages and look for 'com.survey.android' or similarAffected if The app is present on the device
-
Verify the installed version is 3.2.16On Android, go to Settings > Apps > Survey.com Mobile > Version, or use adb: 'adb shell dumpsys package <package_name>' to read the versionInfo. Compare the versionName or versionCode to 3.2.16Affected if The installed version equals exactly 3.2.16
-
Confirm the app transmits sensitive data over networkObserve network traffic from the device using a proxy or network sniffer while using the app to submit survey responses, or review app permissions for network accessAffected if The app sends survey data, credentials, or other sensitive information over the network
-
Test for missing certificate validationSet up a man-in-the-middle proxy with an invalid or self-signed certificate and attempt to intercept traffic from the app. If the connection succeeds without certificate warnings or failures, certificate validation is not occurringAffected if The app accepts connections with invalid, expired, or untrusted certificates without error or warning
A user is affected if the Survey.com Mobile Android app version 3.2.16 is installed and transmits sensitive survey data over network connections without validating SSL/TLS certificates.
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 Android application, including certificate chain verification and hostname validation, with optional certificate pinning for sensitive endpoints.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-6005 — 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-6005 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