LiveActive security incident?Get immediate response
CVE Record

CVE-2017-9588: The "Oritani Mobile Banking" by Oritani Bank app 3.0.0 -- aka oritani-mobile-banking/id778851066 for iOS do...

The "Oritani Mobile Banking" by Oritani Bank app 3.0.0 -- aka oritani-mobile-banking/id778851066 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE describes an iOS mobile banking app that failed to verify server certificates. A person able to intercept the user’s network traffic could impersonate the bank server and capture sensitive information. The sources do not provide a CVSS score, vendor fix, or evidence of active exploitation.

Executive priority

Treat this as a legacy mobile-app exposure with sensitive-data impact. It is not supported by evidence of active exploitation, but any remaining use should be removed because banking credentials and account data may be at risk on intercepted networks.

Technical view

Oritani Mobile Banking for iOS version 3.0.0 did not validate X.509 certificates presented by SSL servers. That breaks the trust check normally used by TLS and enables server spoofing in a man-in-the-middle scenario. The record names crafted certificates as the mechanism, but gives no patch details.

Likely exposure

Exposure appears limited to users or organizations that still have Oritani Mobile Banking for iOS 3.0.0 installed or archived on managed devices. The source bundle does not establish exposure for later app versions, Android apps, backend systems, or other Oritani products.

Exploitation context

The CVE describes a man-in-the-middle risk against mobile users. Successful abuse would require an attacker to intercept traffic and exploit the app’s missing certificate verification. CISA KEV is false in the bundle, and no cited source states active exploitation.

Researcher notes

The public record is sparse: no CVSS, CWE, CPE, fixed version, or vendor advisory is present in the provided bundle. Scope should stay limited to the named iOS app version unless additional vendor evidence expands affected products.

Mitigation direction

  • Identify and remove Oritani Mobile Banking for iOS version 3.0.0 from managed devices.
  • Check current vendor or App Store guidance for supported replacement apps or retired service status.
  • Advise users not to use obsolete mobile banking apps for account access.
  • Consider credential resets for users who accessed banking through the affected app on untrusted networks.

Validation and detection

  • Review MDM, device inventory, or app audit records for Oritani Mobile Banking iOS 3.0.0.
  • Confirm whether the app identifier matches oritani-mobile-banking/id778851066 where inventory data includes it.
  • Check whether any users still rely on archived or unmanaged installations.
  • If testing is required, assess certificate validation only in a controlled lab without real credentials.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-9588 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.