# CVE-2022-37395: Denial of service in CV81-WDM FW

> An input verification flaw in Huawei CV81-WDM devices allows attackers to cause a denial of service.

- **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:** 20 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-hrwv-6jwf-6gwp

## What is CVE-2022-37395?

CVE-2022-37395 is a high-severity denial of service vulnerability in CV81-WDM FW, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Huawei device has an input verification vulnerability. Successful exploitation of this vulnerability may lead to DoS attacks.Affected product versions include:CV81-WDM FW versions 01.70.49.29.46.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Huawei Cv81-Wdm Fw Firmware.

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

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

## Is CVE-2022-37395 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37395 is a high-severity denial of service vulnerability in CV81-WDM FW, published on 20 Sep 2022. 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-2022-37395 in the wild and no public exploit code.

Affected product: CV81-WDM FW. 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-37395/ (Markdown: https://insights.sbomify.com/CVE-2022-37395/index.md)
```

## Sources

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

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