# CVE-2025-2397: China Mobile P22g-CIac Telnet Service improper authorization

> Attackers on the local network can bypass authorization in the Telnet service of China Mobile network devices to gain unauthorized access.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2025
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-33f4-xj2w-x86q

## What is CVE-2025-2397?

CVE-2025-2397 is a medium-severity missing authorization vulnerability in China Mobile GT3200-4G4P, published on 17 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in China Mobile P22g-CIac, ZXWT-MIG-P4G4V, ZXWT-MIG-P8G8V, GT3200-4G4P and GT3200-8G8P up to 20250305. It has been declared as problematic. This vulnerability affects unknown code of the component Telnet Service. The manipulation leads to improper authorization. The attack can only be initiated within the local network. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2025-2397?


## How do I fix CVE-2025-2397?

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

## Is CVE-2025-2397 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2397 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2397 and fix it if it is affected.

What it is: CVE-2025-2397 is a medium-severity missing authorization vulnerability in China Mobile GT3200-4G4P, published on 17 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2397 exists.

Affected product: China Mobile GT3200-4G4P. 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-2025-2397/ (Markdown: https://insights.sbomify.com/CVE-2025-2397/index.md)
```

## Sources

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

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