First State Bank of Yoakum TX Mobile Banking App 3.0.0 on iOS X.509 Certificate Crafted Certificate certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in First State Bank of Yoakum TX Mobile Banking App 3.0.0 on iOS. Impacted is an unknown function of the component X.509 Certificate. Such manipulation as part of Crafted Certificate leads to certificate validation. This vulnerability is uniquely identified as CVE-2017-9586. The attack can be launched remotely. No exploit exists.
Details
A vulnerability, which was classified as critical, has been found in First State Bank of Yoakum TX Mobile Banking App 3.0.0 on iOS (Banking Software). Affected by this issue is an unknown part of the component X.509 Certificate. The manipulation as part of a Crafted Certificate leads to a certificate validation vulnerability. Using CWE to declare the problem leads to CWE-295. The product does not validate, or incorrectly validates, a certificate. Impacted is confidentiality, integrity, and availability. CVE summarizes:
The "FSBY Mobile Banking" by First State Bank of Yoakum TX app 3.0.0 -- aka fsby-mobile-banking/id899136434 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.
The bug was discovered 06/15/2017. The weakness was disclosed 06/16/2017 (Website). The advisory is available at medium.com. This vulnerability is handled as CVE-2017-9586 since 06/12/2017. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1587.003 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-102574, VDB-102575, VDB-102576 and VDB-102577 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Certificate validationCWE: CWE-295 / CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/12/2017 🔍06/15/2017 🔍
06/16/2017 🔍
06/16/2017 🔍
06/16/2017 🔍
10/18/2019 🔍
Sources
Advisory: medium.comStatus: Not defined
CVE: CVE-2017-9586 (🔍)
GCVE (CVE): GCVE-0-2017-9586
GCVE (VulDB): GCVE-100-102602
See also: 🔍
Entry
Created: 06/16/2017 21:15Updated: 10/18/2019 16:09
Changes: 06/16/2017 21:15 (60), 10/18/2019 16:09 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.