Show do Milhao 2014 1.4.6 X.509 Certificate cryptographic issue
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical was found in Show do Milhao 2014 1.4.6. The affected element is an unknown function of the component X.509 Certificate Handler. Such manipulation leads to cryptographic issue. This vulnerability is listed as CVE-2014-5563. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Show do Milhao 2014 1.4.6. Affected by this issue is an unknown function of the component X.509 Certificate Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability. Using CWE to declare the problem leads to CWE-310. Impacted is confidentiality, integrity, and availability. CVE summarizes:
The Show do Milhao 2014 (aka br.com.lgrmobile.sdm) application 1.4.6 for Android 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 weakness was presented 09/08/2014 as confirmed advisory (CERT.org). The advisory is shared for download at kb.cert.org. This vulnerability is handled as CVE-2014-5563 since 08/30/2014. The attack needs to approached within the local network. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1600.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-71433, VDB-71432, VDB-71431 and VDB-71430 for similar entries. Once again VulDB remains the best source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: Cryptographic issueCWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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
08/30/2014 🔍09/08/2014 🔍
09/08/2014 🔍
03/26/2015 🔍
08/24/2024 🔍
Sources
Advisory: kb.cert.orgStatus: Confirmed
CVE: CVE-2014-5563 (🔍)
GCVE (CVE): GCVE-0-2014-5563
GCVE (VulDB): GCVE-100-70868
CERT: 🔍
See also: 🔍
Entry
Created: 03/26/2015 15:08Updated: 08/24/2024 17:33
Changes: 03/26/2015 15:08 (46), 03/18/2019 15:23 (1), 08/24/2024 17:33 (17)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.