# CVE-2024-22069: Permission and Access Control Vulnerability in ZXV10 XT802/ET301

> Attackers with common permissions can escalate privileges to administrator by intercepting password change requests on ZTE terminals.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Aug 2024
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gc3c-rwfr-qx72

## What is CVE-2024-22069?

CVE-2024-22069 is a high-severity vulnerability in ZTE ZXV10 ET301, published on 8 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

There is a permission and access control vulnerability of ZTE's ZXV10 XT802/ET301 product.Attackers with common permissions can log in the terminal web and change the password of the administrator illegally by intercepting requests to change the passwords.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2024-22069?

It affects 2 products.


Products: Zte Zxv10 Et301 Firmware, Zte Zxv10 Xt802 Firmware.

## How do I fix CVE-2024-22069?

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

## Is CVE-2024-22069 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22069 and fix it if it is affected.

What it is: CVE-2024-22069 is a high-severity vulnerability in ZTE ZXV10 ET301, published on 8 Aug 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-22069 in the wild and no public exploit code.

Affected product: ZTE ZXV10 ET301. 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-2024-22069/ (Markdown: https://insights.sbomify.com/CVE-2024-22069/index.md)
```

## Sources

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

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