dbcve.org
Community State Bank LamarApplication · Csb Lamar

CVE-2017-9585

MEDIUM · 5.9 CVSS v3.1 Published 2017-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
The "Community State Bank - Lamar Mobile Banking" by Community State Bank - Lamar app 3.0.3 -- aka community-state-bank-lamar-mobile-banking/id1083927885 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 confidence

The iOS mobile banking app 'Community State Bank - Lamar Mobile Banking' version 3.0.3 fails to validate X.509 certificates from SSL servers during HTTPS connections. This allows an attacker positioned on the network path to intercept and modify traffic by presenting a fraudulent certificate, enabling man-in-the-middle attacks that can steal credentials or session data.

MitigationImplement proper SSL/TLS certificate validation including full certificate chain verification, and consider implementing certificate pinning to ensure the app only trusts the bank's legitimate server certificates.

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
Community State Bank LamarApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the Lamar Mobile Banking app is installed
    On the iOS device, go to Settings > General > iPhone Storage (or Usage on older iOS), or check the home screen for an app named 'Community State Bank - Lamar Mobile Banking' or 'CSB Lamar'. Alternatively, use a mobile device management (MDM) solution or iTunes to list installed apps and look for 'Csb Lamar Community State Bank Lamar' or similar naming.
    Affected if The app is present on the device.
  2. Determine the installed app version
    In the iOS App Store, search for 'Community State Bank Lamar Mobile Banking' or 'Lamar Mobile Banking' and check the current version. If the app is already installed, tap and hold the app icon (or go to Settings > Apps) to view version information. Compare the installed version to the affected version 3.0.3 and note that all versions are listed as affected.
    Affected if The installed version matches 3.0.3 or is any version of this app (since all versions are affected per the CVE).
  3. Verify SSL certificate validation behavior
    Perform a man-in-the-middle (MITM) proxy test using a tool like Burp Suite or OWASP ZAP with a self-signed certificate. Install the proxy CA certificate on the device, configure the device to use the proxy for network traffic, and attempt to access the banking app's HTTPS endpoints. If the app successfully loads and transmits data without certificate validation errors or warnings, the vulnerability is present.
    Affected if The app successfully connects and transmits data through the proxy with an untrusted/self-signed certificate, indicating certificate validation is not occurring.
  4. Inspect network traffic for lack of certificate errors
    Use a network traffic analysis tool (such as Wireshark on a mirrored port, or a mobile-specific proxy) to capture traffic from the app. Attempt to decrypt traffic using an untrusted certificate. If decryption succeeds without the app rejecting the connection, certificate chain validation is not properly implemented.
    Affected if HTTPS traffic from the app can be decrypted using an untrusted certificate without connection failures.

A user is affected if the Community State Bank - Lamar Mobile Banking app is installed on their iOS device, regardless of version, and the app accepts HTTPS connections without validating the server's certificate chain (which can be confirmed by successfully intercepting traffic with an untrusted certificate).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper SSL/TLS certificate validation including full certificate chain verification, and consider implementing certificate pinning to ensure the app only trusts the bank's legitimate server certificates.

Fix this in Community State Bank Lamar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-9585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-9585 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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