# CVE-2021-21732: Information disclosure in <Axon 11 5G>

> Improper access control in ZTE Axon 11 5G allows third-party apps to read sensitive proc files, leading to information disclosure.

- **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:** No
- **Published:** 19 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mjhq-9rgg-c485

## What is CVE-2021-21732?

CVE-2021-21732 is a high-severity vulnerability in <Axon 11 5G>, published on 19 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A mobile phone of ZTE is impacted by improper access control vulnerability. Due to improper permission settings, third-party applications can read some files in the proc file system without authorization. Attackers could exploit this vulnerability to obtain sensitive information. This affects Axon 11 5G ZTE/CN_P725A12/P725A12:10/QKQ1.200816.002/20201116.175317:user/release-keys.

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

It affects 1 product.


Products: Zte Axon 11 5g Firmware.

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

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

## Is CVE-2021-21732 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-21732 is a high-severity vulnerability in <Axon 11 5G>, published on 19 May 2021. 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-21732 in the wild and no public exploit code.

Affected product: <Axon 11 5G>. 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-21732/ (Markdown: https://insights.sbomify.com/CVE-2021-21732/index.md)
```

## Sources

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

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