# CVE-2022-38873: Denial of service in n/a

> Attackers can cause a denial of service on D-Link wireless access points by uploading crafted firmware with modified headers.

- **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 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-j3gx-wf89-g4rx

## What is CVE-2022-38873?

CVE-2022-38873 is a high-severity denial of service vulnerability in n/a, published on 20 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link devices DAP-2310 v2.10rc036 and earlier, DAP-2330 v1.06rc020 and earlier, DAP-2360 v2.10rc050 and earlier, DAP-2553 v3.10rc031 and earlier, DAP-2660 v1.15rc093 and earlier, DAP-2690 v3.20rc106 and earlier, DAP-2695 v1.20rc119_beta31 and earlier, DAP-3320 v1.05rc027 beta and earlier, DAP-3662 v1.05rc047 and earlier allows attackers to cause a Denial of Service (DoS) via uploading a crafted firmware after modifying the firmware header.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 9 products.


Products: Dlink Dap-2310 Firmware, Dlink Dap-2330 Firmware, Dlink Dap-2360 Firmware, Dlink Dap-2553 Firmware, Dlink Dap-2660 Firmware, Dlink Dap-2690 Firmware, Dlink Dap-2695 Firmware, Dlink Dap-3320 Firmware, Dlink Dap-3662 Firmware.

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

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

## Is CVE-2022-38873 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28838](https://insights.sbomify.com/CVE-2021-28838/): Null dereference in n/a (high 7.5)
- [CVE-2021-28839](https://insights.sbomify.com/CVE-2021-28839/): Null dereference in n/a (high 7.5)
- [CVE-2021-28840](https://insights.sbomify.com/CVE-2021-28840/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38873 is a high-severity denial of service vulnerability in n/a, published on 20 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-38873 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-38873/ (Markdown: https://insights.sbomify.com/CVE-2022-38873/index.md)
```

## Sources

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

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