# CVE-2021-40148: Information disclosure in n/a

> Remote attackers can disclose sensitive information from Android Modem EMM due to missing data encryption, requiring no user interaction or privileges.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** A-204728248, ASB-A-204728248, GHSA-qcmm-58xj-wh4r, M-MOLY00716585

## What is CVE-2021-40148?

CVE-2021-40148 is a high-severity vulnerability in Mediatek Nr15, published on 4 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Modem EMM, there is a possible information disclosure due to a missing data encryption. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY00716585; Issue ID: ALPS05886933.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2021-40148?

It affects 6 products.


Products: Mediatek L9, Mediatek Lr11, Mediatek Lr12, Mediatek Lr12a, Mediatek Lr13, Mediatek Nr15.

## How do I fix CVE-2021-40148?

Apply the vendor's patch.

## Is CVE-2021-40148 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-40148 and fix it if it is affected.

What it is: CVE-2021-40148 is a high-severity vulnerability in Mediatek Nr15, published on 4 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-40148 in the wild and no public exploit code.

Affected product: Mediatek Nr15. 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-2021-40148/ (Markdown: https://insights.sbomify.com/CVE-2021-40148/index.md)
```

## Sources

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

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