LaLa Call App up to 2.4.7 on Android X.509 Certificate Validation information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in LaLa Call App up to 2.4.7 on Android. It has been classified as problematic. This issue affects some unknown processing of the component X.509 Certificate Validation. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2017-2103. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability classified as problematic has been found in LaLa Call App up to 2.4.7 on Android (Android App Software). This affects an unknown code block of the component X.509 Certificate Validation. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
The LaLa Call App for Android 2.4.7 and earlier 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 02/03/2017. The weakness was published 04/28/2017 (Website). The advisory is shared at jvn.jp. This vulnerability is uniquely identified as CVE-2017-2103 since 12/01/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 84 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 96004†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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
12/01/2016 🔍02/02/2017 🔍
02/03/2017 🔍
04/28/2017 🔍
04/28/2017 🔍
04/28/2017 🔍
12/21/2020 🔍
Sources
Advisory: jvn.jpResearcher: Yuto Iso
Status: Not defined
CVE: CVE-2017-2103 (🔍)
GCVE (CVE): GCVE-0-2017-2103
GCVE (VulDB): GCVE-100-100665
SecurityFocus: 96004 - LaLa Call App for Android CVE-2017-2103 SSL Certificate Validation Security Bypass Vulnerability
OSVDB: - CVE-2017-2103 - K-Opticom Corporation - Lala Call - Medium
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 04/28/2017 23:46Updated: 12/21/2020 17:19
Changes: 04/28/2017 23:46 (60), 09/21/2020 18:46 (4), 12/21/2020 17:19 (3)
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.