CVE-2014-5708
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 Best Racing/moto Games Ranking (aka com.subapp.android.racing) application 2.2.7 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 Android application 'Best Racing/moto Games Ranking' (com.subapp.android.racing) version 2.2.7 fails to verify X.509 certificates from SSL servers. This means the app does not validate the server's certificate chain, allowing man-in-the-middle attackers to intercept communications by presenting forged certificates and obtain sensitive information such as login credentials or 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.2.7CVSS 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 the vulnerable app is installedRun 'adb shell pm list packages' or check app list in device settings to see if com.subapp.android.racing is presentAffected if The package com.subapp.android.racing is found on the device
-
Check the installed version of the appRun 'adb shell dumpsys package com.subapp.android.racing' and look for versionName or versionCode in the output, or check the app info screen in device settingsAffected if The version shown is 2.2.7 (exact match to the affected version)
-
Verify the app has network capabilitiesRun 'adb shell dumpsys package com.subapp.android.racing' and check for android.permission.INTERNET in the permissions section, or inspect the AndroidManifest.xmlAffected if The app holds INTERNET permission (required for the SSL vulnerability to be exploitable)
-
Confirm the app uses network endpointsUse dynamic analysis: set up a proxy, install the app on a device/emulator, capture traffic with Burp Suite or similar, and observe if the app makes outbound HTTPS requestsAffected if The app transmits data over HTTPS to external servers (the SSL validation flaw affects any such communication)
You are affected if the app com.subapp.android.racing version 2.2.7 is installed on your device and it makes network requests, as the missing SSL certificate validation allows interception of its HTTPS traffic.
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 by verifying the entire certificate chain against trusted CAs, or implement certificate pinning for critical endpoints to ensure the app only accepts expected server certificates.
- 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-5708 — 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-5708 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