CVE-2015-5666
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 · uneditedANA App for Android 3.1.1 and earlier, and ANA App for iOS 3.3.6 and earlier does not verify 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 ANA mobile applications for Android (3.1.1 and earlier) and iOS (3.3.6 and earlier) fail to validate SSL certificates when establishing HTTPS connections. This allows man-in-the-middle attackers to intercept, read, and modify traffic between the app and its backend servers by presenting a fraudulent certificate.
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<= 3.1.1<= 3.3.6CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/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 ANA app on AndroidOpen device Settings > Apps > Application Manager (or Apps) and look for an app named 'ANA' or 'All Nippon Airways' in the installed applications listAffected if The app is present on the device
-
Check ANA app version on AndroidTap on the ANA app in Settings > Apps, then look at the 'Version' or 'Version info' field displayed under the app nameAffected if The displayed version number is 3.1.1 or earlier (for example, 3.1.0, 3.0.5, etc.)
-
Identify ANA app on iOSOn the iOS device home screen, locate the ANA app icon or open Settings > General > iPhone Storage and scroll to find 'ANA' in the app listAffected if The app is present on the device
-
Check ANA app version on iOSOpen the App Store app, search for 'ANA', tap on the ANA app, and note the version number displayed in the app description, or go to Settings > General > iPhone Storage > tap ANA to see versionAffected if The displayed version number is 3.3.6 or earlier (for example, 3.3.5, 3.3.0, etc.)
A user is affected if they have the ANA (All Nippon Airways) mobile app installed with Android version 3.1.1 or earlier, or iOS version 3.3.6 or earlier, because these versions do not validate SSL certificates properly.
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 dataUpdate to Android version 3.2.0 or later and iOS version 3.3.7 or later which implement proper SSL certificate validation. If updates are unavailable, avoid using untrusted networks.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5666 — 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-2015-5666 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