# CVE-2021-41753: Denial of service in n/a

> Remote attackers can disconnect wireless clients from D-Link routers by sending spoofed SAE authentication frames, causing 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:** 27 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rfhg-j76p-857c

## What is CVE-2021-41753?

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

### Official description

A denial-of-service attack in WPA2, and WPA3-SAE authentication methods in D-Link DIR-X1560, v1.04B04, and DIR-X6060, v1.11B04 allows a remote unauthenticated attacker to disconnect a wireless client via sending specific spoofed SAE authentication frames.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

## Which versions are affected by CVE-2021-41753?

It affects 2 products.


Products: Dlink Dir-X1560 Firmware, Dlink Dir-X6060 Firmware.

## How do I fix CVE-2021-41753?

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

## Is CVE-2021-41753 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41753 and fix it if it is affected.

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

## Sources

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

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