CVE-2014-7460
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 Slots Heaven:FREE Slot Machine (aka com.twelvegigs.heaven.slots) application 1.123 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 Slots Heaven:FREE Slot Machine fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept sensitive data 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= free_slot_machineCVSS 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 Slots Heaven app is installedOn Android device, check installed packages via settings or use 'adb shell pm list packages' command to look for package containing 'superluckycasino' or 'slots heaven'Affected if The package 'com.superluckycasino.slotsheaven' or similar is present on the device
-
Determine the installed application versionUse 'adb shell dumpsys package <package_name>' or check app details in Google Play Store / device settings under Apps > Slots HeavenAffected if Version information cannot be obtained or matches the known affected build
-
Verify if the app transmits sensitive dataMonitor network traffic using a proxy like Burp Suite or Charles Proxy to observe if the app makes HTTPS requests and inspect certificate validation behaviorAffected if App makes HTTPS requests to sensitive endpoints without proper certificate validation or shows certificate warnings
-
Check for certificate validation implementationDecompile the APK (using apktool) and inspect source code for SSL/TLS certificate validation methods - look for implementations of TrustManager, hostname verification, or certificate pinningAffected if Code lacks proper certificate validation or uses custom TrustManager that accepts all certificates
-
Assess network interception capabilityConfigure a device proxy with a self-signed certificate and attempt to intercept app traffic - observe if app accepts the proxy certificate without warningAffected if App accepts the proxy CA certificate and traffic flows through without certificate errors
If the Slots Heaven app is installed and transmits data over HTTPS without proper certificate validation, the environment is affected by this vulnerability.
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 validation using Android's built-in certificate validation mechanisms or certificate pinning to ensure the application only trusts legitimate 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-7460 — 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-7460 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