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

> Attackers can cause a denial of service on D-Link DIR-819 routers by sending a crafted request with a specific sys_token parameter.

- **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:** 16 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-xj5r-2vxf-3ch7

## What is CVE-2022-40946?

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

### Official description

On D-Link DIR-819 Firmware Version 1.06 Hardware Version A1 devices, it is possible to trigger a Denial of Service via the sys_token parameter in a cgi-bin/webproc?getpage=html/index.html request.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Dlink Dir-819 Firmware.

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

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

## Is CVE-2022-40946 being exploited?

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

Public exploit code:

- DLink DIR 819 A1 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-38258](https://insights.sbomify.com/CVE-2022-38258/): Path traversal in n/a (high 8.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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