CVE-2016-4840
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 · uneditedCoordinate Plus App for Android 1.0.2 and earlier and Coordinate Plus App for iOS 1.0.2 and earlier do 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 Coordinate Plus mobile applications for Android and iOS versions 1.0.2 and earlier fail to validate SSL/TLS certificates during HTTPS connections. This allows man-in-the-middle attackers to intercept, read, and modify encrypted traffic by presenting invalid or self-signed certificates, since the app accepts any certificate 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.0.2CVSS 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.1/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.
-
Check if Coordinate Plus app is installedOn Android: Open Settings > Apps and search for 'Coordinate Plus'. On iOS: Search for 'Coordinate Plus' in the App Library or on the Home ScreenAffected if Coordinate Plus app is found on the device
-
Determine installed version on AndroidGo to Settings > Apps > Coordinate Plus and read the version number displayed under 'App info' or 'Version'Affected if Version displays as 1.0.2 or lower
-
Determine installed version on iOSOpen the App Store, search for 'Coordinate Plus', tap on the app, and note the version number shown in the app descriptionAffected if Version displays as 1.0.2 or lower
-
Confirm affected statusCompare your identified version against the affected range: versions 1.0.2 and earlier are vulnerable. Versions 1.0.3 and later include the fixAffected if Installed version is 1.0.2 or earlier
If the Coordinate Plus app version is 1.0.2 or earlier, the app is vulnerable because it accepts any SSL certificate without validation, allowing traffic interception.
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 Coordinate Plus App version 1.0.3 or later which implements proper SSL certificate validation. Until then, avoid using the app on untrusted networks.
- Consultation2.0 h
- Implementation10.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 $5,056.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-4840 — 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-4840 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