CVE-2017-9577
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 "First Citizens Bank-Mobile Banking" by First Citizens Bank (AL) app 3.0.0 -- aka first-citizens-bank-mobile-banking/id566037101 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 First Citizens Bank Mobile Banking iOS app version 3.0.0 fails to validate X.509 certificates from SSL servers, allowing man-in-the-middle attackers to intercept encrypted communications by presenting fraudulent certificates. This enables credential theft and session hijacking when users access the banking service over untrusted networks.
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.0.0CVSS 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 First Citizens Bank Mobile app is installedOn the iOS device, go to Settings > General > iPhone Storage (or Settings > Apps on newer iOS), or check the home screen for the app icon labeled 'First Citizens Bank' or 'FCBI'Affected if The app is present on any iOS device in the organization
-
Verify the installed app version is 3.0.0Open the App Store app, search for 'First Citizens Bank Mobile' or 'FCBI', tap on the app, and scroll to the Version information. Alternatively, access the app through MDM or mobile device management console to retrieve the installed version.Affected if The displayed version is exactly 3.0.0
-
Confirm the app is in active useCheck enterprise MDM logs or network logs for connections to First Citizens Bank servers originating from iOS devices. Query MDM for app installation and launch status.Affected if Users are actively launching and using the version 3.0.0 app to access banking services
-
Verify certificate validation is bypassed (optional deeper check)Configure a MITM proxy (such as Burp Suite or Charles Proxy) with an invalid or self-signed certificate on a test device, install the proxy CA certificate on the device, then attempt to intercept traffic while using the app to access banking featuresAffected if The app successfully connects and displays banking content despite the proxy presenting an invalid certificate (this confirms the vulnerability is present)
A user is affected if they have the First Citizens Bank Mobile iOS app version 3.0.0 installed and actively use it to access banking services, as this version lacks SSL certificate validation allowing credential theft via man-in-the-middle 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 SSL/TLS certificate validation in the app's networking code, preferably through certificate pinning for the bank's specific certificate(s), to ensure the app only trusts the legitimate server's certificate.
- Consultation2.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,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9577 — 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-9577 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