# CVE-2021-21742: Information disclosure in ZTE Axon 30 Pro Message Service App

> Attackers can access specific pages in the ZTE Axon 30 Pro message service app to obtain sensitive user information due to improper parameter settings.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j3r4-cf7v-p9gf

## What is CVE-2021-21742?

CVE-2021-21742 is a medium-severity vulnerability in ZTE Axon 30 Pro Message Service App, published on 24 Sep 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

There is an information leak vulnerability in the message service app of a ZTE mobile phone. Due to improper parameter settings, attackers could use this vulnerability to obtain some sensitive information of users by accessing specific pages.

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

It affects 1 product.


Products: Zte Axon 30 Pro Message Service.

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

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

## Is CVE-2021-21742 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-21742 is a medium-severity vulnerability in ZTE Axon 30 Pro Message Service App, published on 24 Sep 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-21742 in the wild and no public exploit code.

Affected product: ZTE Axon 30 Pro Message Service App. 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-21742/ (Markdown: https://insights.sbomify.com/CVE-2021-21742/index.md)
```

## Sources

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

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