Jpmorganchase Chase mobile X509TrustManager input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Jpmorganchase Chase mobile. This vulnerability affects unknown code of the component X509TrustManager. This manipulation causes input validation. This vulnerability is tracked as CVE-2012-5810. No exploit exists.
Details
A vulnerability classified as critical was found in Jpmorganchase Chase mobile (the affected version is unknown). Affected by this vulnerability is an unknown code of the component X509TrustManager. The manipulation with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
The Chase mobile banking application for Android does not verify that the server hostname matches a domain name in the subject s Common Name (CN) or subjectAltName field of the X.509 certificate, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate, related to overriding the default X509TrustManager.
The weakness was disclosed 11/04/2012 (Website). The advisory is shared at cs.utexas.edu. This vulnerability is known as CVE-2012-5810 since 11/04/2012. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-62870, VDB-62858, VDB-62856 and VDB-62855 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.5
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Input validationCWE: CWE-20
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
11/04/2012 🔍11/04/2012 🔍
11/04/2012 🔍
03/24/2015 🔍
02/11/2018 🔍
Sources
Advisory: cs.utexas.eduStatus: Not defined
CVE: CVE-2012-5810 (🔍)
GCVE (CVE): GCVE-0-2012-5810
GCVE (VulDB): GCVE-100-62857
See also: 🔍
Entry
Created: 03/24/2015 12:22Updated: 02/11/2018 11:54
Changes: 03/24/2015 12:22 (40), 02/11/2018 11:54 (6)
Complete: 🔍
Cache ID: 216:29D:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.