CVE-2016-1187
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 · uneditedCybozu KUNAI for iPhone 2.0.3 through 3.1.5 and for Android 2.1.2 through 3.0.4 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 Cybozu KUNAI mobile application fails to validate SSL certificates when establishing HTTPS connections, allowing an attacker to intercept and modify communications between the app and server via man-in-the-middle attacks. This affects both iOS versions 2.0.3-3.1.5 and Android versions 2.1.2-3.0.4.
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= 2.1.2= 2.1.3= 3.0.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 2.0.3= 2.0.3.1= 2.0.4= 2.0.5= 2.1.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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 Cybozu KUNAI installation on iOSCheck the app version in the iOS App Store app listing, or within the app itself by tapping the settings icon, or via iTunes/Finder when the device is connectedAffected if The installed iOS version falls within 2.0.3 through 3.1.5 inclusive
-
Identify Cybozu KUNAI installation on AndroidCheck the app version in the Google Play Store listing, or open the device Settings > Apps > Cybozu KUNAI to view the version informationAffected if The installed Android version falls within 2.1.2 through 3.0.4 inclusive
-
Compare installed version against affected rangesReview the specific version number obtained from step 1 or step 2 and compare it to the affected version lists for the relevant platformAffected if The installed version matches any of these: 2.0.3, 2.0.3.1, 2.0.4, 2.0.5, 2.1.0, 2.1.2, 2.1.3, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4 (for Android); or 2.0.3-3.1.5 (for iOS)
If Cybozu KUNAI is installed at an affected version on either iOS or Android, the app is vulnerable to SSL certificate validation bypass and the traffic can be intercepted via man-in-the-middle attacks.
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 verification by validating the certificate chain against trusted root CAs and/or implementing certificate pinning to ensure the app only trusts specific 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-2016-1187 — 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-1187 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