CVE-2014-5987
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 My3 - by 3HK (aka com.my3) application @7F0A0001 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 My3 Android application fails to validate X.509 certificates from SSL servers, accepting any certificate presented during TLS connections instead of verifying against trusted Certificate Authorities. This allows attackers on the same network to perform man-in-the-middle attacks, intercepting and modifying encrypted traffic by presenting forged 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= \@7f0a0001CVSS 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 My3 app is installedOn Android device: Settings > Apps > look for 'My3' or 'Three My3' in the app list. Or use ADB command: `adb shell pm list packages | grep -i my3`Affected if The My3 application is present on the device
-
Identify installed My3 versionIn Android Settings > Apps > My3 > App info, view the Version or Version code. Or use ADB: `adb shell dumpsys package com.three.my3 | grep versionName` or `adb shell dumpsys package com.three.my3 | grep versionCode`Affected if The version matches or is earlier than the affected build 7f0a0001
-
Verify app makes network connectionsCheck if the app has internet permission and is configured for network use. Use network monitoring tools like Android Studio Profiler or third-party apps to observe if My3 initiates SSL/TLS connectionsAffected if The app actively makes HTTPS connections to server endpoints
-
Confirm SSL validation behavior (requires code inspection or testing)Use a network proxy like Burp Suite or OWASP ZAP with a self-signed certificate. Attempt MITM interception - if the app accepts the proxy certificate without warning or error, certificate validation is not properly implementedAffected if The app accepts untrusted or forged certificates during TLS connections without validation errors
If the Three My3 Android app version 7f0a0001 or earlier is installed and the app makes network connections, the device is vulnerable to MITM attacks due to improper SSL certificate validation.
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 app by using a TrustManager that validates certificates against trusted CAs, or implement certificate pinning for known server certificates.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5987 — 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-5987 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