CVE-2017-9560
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 cayuga-lake-national-bank/id1151601539 app 4.0.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 iOS banking app version 4.0.1 fails to validate X.509 certificates from SSL/TLS servers, meaning the app accepts any certificate presented by a server without verification. This allows man-in-the-middle attackers to intercept encrypted communications by presenting a fraudulent certificate, enabling them to capture sensitive credentials and financial 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= 4.0.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 the Cayuga Lake National Bank iOS app is installedCheck iOS devices or mobile device management (MDM) inventory for the presence of the Cayuga Lake National Bank app (package identifier may be related to 'cayugalakenationalbank' or 'cayugalakenationalbank.com').Affected if The app is present on any managed iOS device.
-
Determine the installed version of the appOn iOS, check the app version in Settings > General > iPhone Storage > Cayuga Lake National Bank, or via MDM/enterprise mobility management tools that report installed app versions.Affected if The installed version is exactly 4.0.1.
-
Compare your installed version to the affected rangeIf the app version is available, compare it to the affected version 4.0.1. Note that the vulnerability specifically affects version 4.0.1; other versions may have different behavior.Affected if The app version is 4.0.1 and the app makes network requests.
-
Verify SSL/TLS certificate validation behaviorSince this is a code-level vulnerability (lack of X.509 certificate validation), confirm via dynamic analysis or code review that the app does not validate server certificates. This would require intercepting app traffic with a proxy using a self-signed cert to see if the app accepts it.Affected if The app accepts connections to a server with an untrusted or self-signed certificate without warning or rejection.
If the Cayuga Lake National Bank iOS app version 4.0.1 is installed and makes network connections, the environment is affected by this vulnerability.
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 certificate validation using certificate pinning or standard X.509 chain verification in all network requests to ensure the app only trusts legitimate server certificates.
- Consultation4.0 h
- Implementation8.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9560 — 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-9560 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