# CVE-2022-45957: Memory corruption in n/a

> A remote stack buffer overflow in ZTE ZXHN-H108NS routers allows attackers to execute arbitrary code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-vj96-vq8w-xwrw

## What is CVE-2022-45957?

CVE-2022-45957 is a high-severity memory corruption vulnerability in n/a, published on 12 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZTE ZXHN-H108NS router with firmware version H108NSV1.0.7u_ZRD_GR2_A68 is vulnerable to remote stack buffer overflow.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-45957?

It affects 1 product.


Products: Zte Zxhn-H108ns Firmware.

## How do I fix CVE-2022-45957?

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

## Is CVE-2022-45957 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45957 and fix it if it is affected.

What it is: CVE-2022-45957 is a high-severity memory corruption vulnerability in n/a, published on 12 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45957 exists.

Affected product: n/a. 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-2022-45957/ (Markdown: https://insights.sbomify.com/CVE-2022-45957/index.md)
```

## Sources

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

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