MakeMyTrip 7.2.4 on Android Database File databases information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in MakeMyTrip 7.2.4 on Android. The affected element is an unknown function of the file data/com.makemytrip/databases of the component Database File. Executing a manipulation can lead to information disclosure. This vulnerability is handled as CVE-2018-11242. It is possible to launch the attack on the local host. Additionally, an exploit exists.
Details
A vulnerability classified as problematic was found in MakeMyTrip 7.2.4 on Android (Android App Software). This vulnerability affects some unknown functionality of the file data/com.makemytrip/databases of the component Database File. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
An issue was discovered in the MakeMyTrip application 7.2.4 for Android. The databases (locally stored) are not encrypted and have cleartext that might lead to sensitive information disclosure, as demonstrated by data/com.makemytrip/databases and data/com.makemytrip/Cache SQLite database files.
The bug was discovered 05/20/2018. The weakness was released 05/20/2018 (Website). The advisory is shared for download at gist.github.com. This vulnerability was named CVE-2018-11242 since 05/18/2018. The attack needs to be approached locally. A single authentication is required for exploitation. Technical details and also a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1592.
It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.
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 Exploit-DB (44690). Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Timeline
05/18/2018 🔍05/20/2018 🔍
05/20/2018 🔍
05/20/2018 🔍
05/20/2018 🔍
06/10/2024 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2018-11242 (🔍)
GCVE (CVE): GCVE-0-2018-11242
GCVE (VulDB): GCVE-100-118036
scip Labs: https://www.scip.ch/en/?labs.20130704
Entry
Created: 05/20/2018 23:52Updated: 06/10/2024 14:51
Changes: 05/20/2018 23:52 (59), 02/07/2020 14:37 (4), 06/10/2024 14:51 (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.