CVE-2016-1184
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 · uneditedTokyo Star bank App for Android before 1.4 and Tokyo Star bank App for iOS before 1.4 do not validate SSL certificates.
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 Tokyo Star Bank mobile applications for Android (before version 1.4) and iOS (before version 1.4) fail to validate SSL certificates during HTTPS connections. This allows an attacker performing a man-in-the-middle (MITM) attack to intercept and modify encrypted communications between the app and the server by presenting a fraudulent certificate that the app will accept without verification.
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.3CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
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 the Tokyo Star Bank app on your Android deviceOpen device Settings, go to Apps or Applications, find and select 'Tokyo Star Bank' from the app list, then view the version information displayed under the app nameAffected if The displayed version number is 1.3 or lower (for example, 1.3, 1.2, 1.1, 1.0)
-
Identify the Tokyo Star Bank app on your iOS deviceOpen the Settings app, go to General, tap iPhone Storage or Storage & iCloud Usage, scroll to find 'Tokyo Star Bank' in the app list, and view the version number shownAffected if The displayed version number is 1.3 or lower (for example, 1.3, 1.2, 1.1, 1.0)
-
Check the app version via Google Play Store (Android)Open the Google Play Store app, search for 'Tokyo Star Bank' or 'Tokyo Star Bank mobile', tap on the app, and view the version number in the app listingAffected if The version shown is 1.3 or earlier, indicating the vulnerable version is installed
-
Check the app version via Apple App Store (iOS)Open the App Store app, search for 'Tokyo Star Bank', tap on the app, and view the version information displayedAffected if The version shown is 1.3 or earlier, indicating the vulnerable version is installed
You are affected if you have version 1.3 or any earlier version of the Tokyo Star Bank app installed on either your Android or iOS device.
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 dataUpgrade both the Android and iOS versions of the Tokyo Star Bank app to version 1.4 or later, which includes proper SSL certificate validation. Until upgraded, users should avoid using untrusted networks (e.g., public WiFi) with the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1184 — 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-2016-1184 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