CVE-2017-3212
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 Space Coast Credit Union Mobile app 2.2 for iOS and 2.1.0.1104 for Android does 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 Space Coast Credit Union Mobile apps for iOS (2.2) and Android (2.1.0.1104) fail to validate SSL/TLS server certificates, allowing attackers to intercept encrypted communications via man-in-the-middle attacks and capture sensitive banking credentials and transaction data.
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.0.1104<= 2.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 Space Coast Credit Union Android app is installedOn the Android device, go to Settings > Apps > find 'SCCU' or 'Space Coast Credit Union' in the installed apps list. Alternatively, use ADB: adb shell pm list packages | grep sccuAffected if The app 'com.sccu.mobile' or similar SCCU package is found on the device
-
Verify Android app version against affected rangeIn Settings > Apps > Space Coast Credit Union, view the Version info. On Android, you can also use: adb shell dumpsys package <package_name> | grep versionNameAffected if The installed version is 2.1.0.1104 or any lower version number (the affected range is <= 2.1.0.1104)
-
Check if Space Coast Credit Union iOS app is installedOn the iOS device, check the App Library or home screen for the SCCU or Space Coast Credit Union app icon. On a Mac with iTunes/Finder, navigate to the device's installed apps sectionAffected if The SCCU mobile banking app for iOS is present on the device
-
Verify iOS app version against affected rangeLong-press the app icon on iOS and select 'App Info' or go to Settings > SCCU to view the version number. In iTunes/Finder (if older iOS), right-click the app and select Get InfoAffected if The installed version is 2.2 or any lower version number (the affected range is <= 2.2)
A user is affected if they have installed the Space Coast Credit Union mobile app on Android (version 2.1.0.1104 or lower) or iOS (version 2.2 or lower), as these versions fail to validate SSL/TLS certificates and are vulnerable to credential interception via MITM 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 X.509 certificate chain validation and consider certificate pinning to ensure the app only trusts the legitimate banking server's certificate, preventing MITM attacks.
- Consultation4.0 h
- Implementation12.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 $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3212 — 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-2017-3212 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