# CVE-2021-21733: Information disclosure in <ZXCDN V7.01>

> Attackers can obtain sensitive information from the ZXCDN management system to facilitate further analysis and potential attacks.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-36w9-8j3m-6mcg

## What is CVE-2021-21733?

CVE-2021-21733 is a medium-severity vulnerability in <ZXCDN V7.01>, published on 19 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The management system of ZXCDN is impacted by the information leak vulnerability. Attackers can make further analysis according to the information returned by the program, and then obtain some sensitive information. This affects ZXCDN V7.01 all versions up to IAMV7.01.01.02.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Zte Zxcdn.

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

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

## Is CVE-2021-21733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-21733 is a medium-severity vulnerability in <ZXCDN V7.01>, published on 19 May 2021. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-21733 in the wild and no public exploit code.

Affected product: <ZXCDN V7.01>. 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-21733/ (Markdown: https://insights.sbomify.com/CVE-2021-21733/index.md)
```

## Sources

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

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