CVE-2014-5587
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 brokenscreencrank (aka com.biggame.brokenscreencrank) application 1.1 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 brokenscreencrank Android application version 1.1 fails to verify X.509 certificates from SSL servers during secure communications. This allows man-in-the-middle attackers to intercept traffic by presenting crafted (potentially self-signed or expired) certificates, enabling server spoofing and theft of sensitive data transmitted over what should be encrypted channels.
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= 1.1CVSS 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 brokenscreencrank app is installedOn the Android device, navigate to Settings > Apps > All Apps, or use ADB command: 'adb shell pm list packages | grep brokenscreencrank'Affected if The brokenscreencrank package is found on the device
-
Identify the installed versionIn Settings > Apps > All Apps, tap on brokenscreencrank and view the Version info, or use ADB: 'adb shell dumpsys package com.brokenscreencrank'Affected if The displayed version is 1.1
-
Verify network traffic usageUse a network monitoring tool (such as packet capture or Android Studio Network Profiler) to observe if the app transmits sensitive data over HTTPS connectionsAffected if The app sends sensitive information (credentials, personal data, financial details) over network without proper SSL validation
-
Inspect SSL implementation in APKIf the APK is available, decompile it (using apktool or similar) and search for custom TrustManager implementations, disabled hostname verification, or empty certificate validators in the source codeAffected if Code shows disabled certificate validation, custom TrustManager that accepts all certificates, or missing certificate chain verification
If brokenscreencrank version 1.1 is installed and transmits sensitive data over the network without proper SSL/TLS certificate validation, the device is vulnerable to CVE-2014-5587.
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 chain validation in the application using standard TrustManager configurations, preferably with certificate pinning for high-security endpoints, to ensure the app verifies server certificates against trusted Certificate Authorities.
- 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-5587 — 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-5587 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