CVE-2016-7805
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 mobiGate App for Android version 2.2.1.2 and earlier and mobiGate App for iOS version 2.2.4.1 and earlier do 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 mobiGate mobile applications for Android (versions 2.2.1.2 and earlier) and iOS (versions 2.2.4.1 and earlier) fail to validate X.509 certificates during SSL/TLS server connections. This allows man-in-the-middle attackers to intercept communications by presenting forged certificates, enabling them to spoof legitimate servers and capture sensitive data transmitted by the app.
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.2.1.2<= 2.2.4.1CVSS 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 if mobiGate is installed on AndroidCheck device for the mobiGate app. On Android, verify the installed package exists and note its version number from the app info screen or via adb: adb shell dumpsys package com.unisys.mobigate (adjust package name if different)Affected if mobiGate is installed on Android with version 2.2.1.2 or lower
-
Identify if mobiGate is installed on iOSCheck device for the mobiGate app. On iOS, locate the app on the home screen and check the version in the App Store or in Settings > General > iPhone Storage (if available)Affected if mobiGate is installed on iOS with version 2.2.4.1 or lower
-
Verify the exact installed versionCompare the installed version number against the affected ranges: Android <= 2.2.1.2 and iOS <= 2.2.4.1. Obtain the version from the app's about or settings screen, or from the app store listing if already installedAffected if The installed version falls within or below the affected version ranges for the respective platform
-
Confirm SSL/TLS certificate validation status (optional for security teams)If you have access to the app binary or source code, review the network code to verify whether X.509 certificate chain validation and hostname verification are implemented. Alternatively, use a proxy tool to test whether the app accepts a self-signed certificate - if it does, validation may be disabledAffected if The app accepts invalid or self-signed certificates, confirming the certificate validation vulnerability is present
A user is affected if they have mobiGate installed with Android version 2.2.1.2 or earlier, or iOS version 2.2.4.1 or earlier, and the app fails to validate SSL/TLS certificates.
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/TLS certificate validation in both Android and iOS versions of the mobiGate app, including chain-of-trust verification, hostname validation, and optionally certificate pinning for added security.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-7805 — 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-7805 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