Bank of Tokyo-Mitsubishi UFJ App up to 5.2.2/5.3.1 TLS cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Bank of Tokyo-Mitsubishi UFJ App up to 5.2.2/5.3.1. This vulnerability affects unknown code of the component TLS Handler. Performing a manipulation results in cryptographic issue. This vulnerability is known as CVE-2016-7812. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability, which was classified as critical, was found in Bank of Tokyo-Mitsubishi UFJ App up to 5.2.2/5.3.1 (Banking Software). This affects an unknown code of the component TLS Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability. CWE is classifying the issue as CWE-310. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
The Bank of Tokyo-Mitsubishi UFJ, Ltd. App for Android ver5.3.1, ver5.2.2 and earlier allow a man-in-the-middle attacker to downgrade the communication between the app and the server from TLS v1.2 to SSL v3.0, which may result in the attacker to eavesdrop on an encrypted communication.
The bug was discovered 12/06/2016. The weakness was published 08/02/2017 (Website). The advisory is shared at securityfocus.com. This vulnerability is uniquely identified as CVE-2016-7812 since 09/09/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 239 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 vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94829†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.1
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.1
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: Cryptographic issueCWE: CWE-310
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
09/09/2016 🔍12/06/2016 🔍
12/06/2016 🔍
08/02/2017 🔍
08/02/2017 🔍
08/02/2017 🔍
01/07/2021 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Reo Yoshida
Status: Not defined
CVE: CVE-2016-7812 (🔍)
GCVE (CVE): GCVE-0-2016-7812
GCVE (VulDB): GCVE-100-104745
SecurityFocus: 94829 - Bank of Tokyo Mitsubishi UFJ CVE-2016-7812 Man in the Middle Information Disclosure Vulnerability
Entry
Created: 08/02/2017 22:26Updated: 01/07/2021 07:23
Changes: 08/02/2017 22:26 (60), 11/03/2019 08:07 (3), 01/07/2021 07:23 (2)
Complete: 🔍
Cache ID: 216::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.