# CVE-2018-11242: Information disclosure in n/a

> Attackers can access sensitive cleartext data from unencrypted local SQLite databases in the MakeMyTrip Android application.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3cmf-2r4c-r97p

## What is CVE-2018-11242?

CVE-2018-11242 is a medium-severity vulnerability in n/a, published on 20 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2018-11242?

It affects 1 product.


Products: Makemytrip Makemytrip.

## How do I fix CVE-2018-11242?

No fix has been published for CVE-2018-11242 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-11242 being exploited?

There is no known exploitation of CVE-2018-11242 in the wild and no public exploit code.

Public exploit code:

- MakeMyTrip 7.2.4 - Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11242 and fix it if it is affected.

What it is: CVE-2018-11242 is a medium-severity vulnerability in n/a, published on 20 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11242 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-11242/ (Markdown: https://insights.sbomify.com/CVE-2018-11242/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-11242
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-11242
- OSV: https://osv.dev/vulnerability/CVE-2018-11242

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-11242/
Summaries are generated and may contain mistakes; the official description above is the record.