CVE-2017-5914
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 DOT IT Banque Zitouna app 2.1 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 DOT IT Banque Zitouna iOS app version 2.1 fails to validate X.509 certificates from SSL/TLS servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates and capture sensitive data transmitted between the app and backend servers.
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.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.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.
-
Identify if the Banque Zitouna iOS app is installedOn the iOS device, navigate to Settings > General > iPhone Storage (or Settings > Apps on newer iOS), then search for 'Banque Zitouna' or 'DOT IT' to locate the installed appAffected if The app is present on the device
-
Determine the installed version of the Banque Zitouna appIn the iOS app list (Settings > General > iPhone Storage), tap on the Banque Zitouna app to display its version number. Alternatively, open the App Store, search for the app, and check the version information listedAffected if The version displayed is exactly 2.1
-
Verify the app connects to backend servers over SSL/TLSUse a network proxy tool (such as Burp Suite or OWASP ZAP) configured with an invalid certificate to intercept traffic between the iOS app and its servers. Attempt to proxy the app's network trafficAffected if The app successfully establishes SSL/TLS connections despite the proxy presenting an invalid/fraudulent certificate, indicating no certificate validation is performed
-
Confirm the app lacks certificate pinningAnalyze the app's network configuration by inspecting the binary or using a tool like Frida to hook SSL/TLS functions. Check if the app validates only a specific certificate or certificate chain rather than accepting any valid certificateAffected if The app accepts connections to the backend without verifying the server's certificate against a pinned certificate or chain
The user is affected if the Banque Zitouna iOS app version 2.1 is installed and the app accepts SSL/TLS connections without properly validating the server's X.509 certificate chain.
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 including certificate pinning to ensure the app only trusts the legitimate server's certificate chain.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5914 — 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-5914 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