CVE-2014-5785
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 Bouncy Bill World-Cup (aka mominis.Generic_Android.Bouncy_Bill_World_Cup) application 1.0.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 Bouncy Bill World-Cup Android application version 1.0.1 fails to validate X.509 certificates from SSL servers, enabling man-in-the-middle attackers to spoof servers and intercept sensitive data transmitted over HTTPS connections.
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.0.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.
-
Identify installed version of Bouncy Bill World CupOn Android device or emulator, go to Settings > Apps > Bouncy Bill World Cup (or Playscape Bouncy Bill World Cup) and check the version number under App Info. Alternatively, use ADB: adb shell pm list packages | grep -i bouncy, then adb shell dumpsys package <package_name> | grep versionNameAffected if Version displayed is exactly 1.0.1
-
Determine if the app uses network connectionsUse a network sniffer (like Wireshark or Android Packet Capture) while the app is running to observe outgoing connections. Alternatively, check AndroidManifest.xml for INTERNET permission within the APKAffected if The app makes HTTP/HTTPS requests to external servers and the INTERNET permission is present in the manifest
-
Extract and inspect the APK for SSL validation codeObtain the APK (from adb or app store), decompile using apktool or jadx, then search source code for HTTPS/SSL implementation. Look for custom TrustManager, hostnameVerifier, or HttpsURLConnection usage. Search for patterns like 'TrustManager' or 'hostnameVerifier' that bypass validationAffected if Code contains custom TrustManager or hostnameVerifier implementations that accept all certificates, or uses ALLOW_ALL_HOSTNAME_VERIFIER, or lacks certificate chain validation entirely
You are affected if Bouncy Bill World Cup version 1.0.1 is installed AND the app transmits data over HTTPS AND the code does not properly validate X.509 certificate chains or hostnames.
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 X.509 certificate validation within the application's network layer, including hostname verification and chain-of-trust validation. Consider implementing certificate pinning for added security against MITM attacks.
- 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-5785 — 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-5785 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