# CVE-2022-38955: Security feature bypass in n/a

> An attacker can bypass firmware integrity checks via MITM to install malicious firmware, enabling backdoors or denial of service on Netgear extenders.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Sep 2022
- **Updated:** 28 May 2025
- **Also known as:** GHSA-m2rw-gwp5-6wqw

## What is CVE-2022-38955?

CVE-2022-38955 is a high-severity vulnerability in n/a, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An exploitable firmware modification vulnerability was discovered on the Netgear WPN824EXT WiFi Range Extender. An attacker can conduct a MITM attack to modify the user-uploaded firmware image and bypass the CRC check. A successful attack can either introduce a backdoor to the device or make the device DoS. This affects Firmware Version: 1.1.1_1.1.9.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

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

It affects 1 product.


Products: Netgear Wpn824ext Firmware.

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

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

## Is CVE-2022-38955 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38956](https://insights.sbomify.com/CVE-2022-38956/): Security feature bypass in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38955 is a high-severity vulnerability in n/a, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-38955 in the wild and no public exploit code.

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-38955/ (Markdown: https://insights.sbomify.com/CVE-2022-38955/index.md)
```

## Sources

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

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