CVE-2014-7087
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 Top Roller Coasters Europe 1 (aka com.appaapps.top10tallesteuropeanrollercoasters1) application @7F050001 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 'Top Roller Coasters Europe 1' fails to validate X.509 certificates from SSL/TLS servers during HTTPS connections. This allows an attacker positioned on the same network to intercept and modify traffic by presenting a fraudulent certificate, enabling credential theft, data injection, or session hijacking.
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= \@7f050001CVSS 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.
-
Confirm the app is installedOn the Android device, go to Settings > Apps > Downloaded, or use ADB command: pm list packages | grep -i 'rollercoasters'Affected if The package com.appapps.toprollercoasterseurope or similar is present
-
Identify the installed versionIn Settings > Apps > Top Roller Coasters Europe > Version info, or use ADB: dumpsys package <package_name> | grep versionNameAffected if Version is 7f050001 or the app was downloaded prior to any patch
-
Verify the app makes network requestsObserve if the app connects to the internet - use network monitoring or check app permissions for INTERNET access via: pm dump <package_name> | grep -i permissionAffected if The app has INTERNET permission and makes HTTPS requests to its servers
-
Confirm vulnerability is exploitableSince this is a code-level flaw (missing SSL validation), no config toggle exists. The vulnerability exists if the app processes HTTPS responses without validating the certificate chainAffected if The app accepts HTTPS connections without proper X.509 certificate verification - observable via MITM proxy test if traffic can be intercepted
User is affected if the Android app 'Top Roller Coasters Europe 1' version 7f050001 is installed and makes HTTPS network requests, as the app lacks proper SSL certificate validation in its code.
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 using certificate pinning or standard X.509 chain verification in the Android application's network layer to ensure connections only trust legitimate server certificates.
- Consultation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7087 — 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-7087 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