CVE-2017-5911
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 Banco Santander Mexico SA Supermovil app 3.5 through 3.7 for iOS 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 Banco Santander Mexico SA Supermovil app versions 3.5 through 3.7 for iOS fails to verify X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting a crafted certificate and spoof the legitimate server.
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.5= 3.6= 3.7CVSS 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 Supermovil app is installedCheck iOS devices for the Banco Santander Mexico SA Supermovil app - look for the app icon labeled 'Supermovil' in the app library or on the home screenAffected if The app is present on any iOS device
-
Check the installed app versionOpen the App Store, tap your profile icon, tap 'Purchased', find 'Supermovil', and view the version number. Alternatively, open the app and navigate to Settings or About section to find the versionAffected if Version displays as 3.5, 3.6, or 3.7
-
Verify version against affected rangeCompare the found version number to the affected versions: 3.5, 3.6, and 3.7Affected if The installed version is exactly 3.5, 3.6, or 3.7
-
Confirm SSL certificate validation is not performedThis vulnerability exists when the app does not validate SSL/TLS certificates. Test by attempting to connect through a proxy with an untrusted certificate - if the app functions normally without warnings, certificate validation is not occurringAffected if The app accepts connections through a man-in-the-middle proxy with an untrusted or mismatched certificate
If the Banco Santander Mexico SA Supermovil app version is 3.5, 3.6, or 3.7 on an iOS device, the SSL certificate validation flaw is present and communications can be intercepted.
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 the app to a version that implements proper SSL/TLS certificate validation, including certificate chain verification, hostname validation, and preferably certificate pinning for sensitive endpoints.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5911 — 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-5911 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