# CVE-2018-18907: Auth bypass in n/a

> Attackers can bypass wireless authentication on D-Link DIR-850L routers by sending unencrypted data frames, gaining unauthorized network access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2022
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fj7h-v25q-fvpr

## What is CVE-2018-18907?

CVE-2018-18907 is a high-severity authentication bypass vulnerability in n/a, published on 16 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on D-Link DIR-850L 1.21WW devices. A partially completed WPA handshake is sufficient for obtaining full access to the wireless network. A client can access the network by sending packets on Data Frames to the AP without encryption.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-18907?

It affects 1 product.


Products: Dlink Dir-850l Firmare.

## How do I fix CVE-2018-18907?

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

## Is CVE-2018-18907 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18907 and fix it if it is affected.

What it is: CVE-2018-18907 is a high-severity authentication bypass vulnerability in n/a, published on 16 Jun 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-2018-18907 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-2018-18907/ (Markdown: https://insights.sbomify.com/CVE-2018-18907/index.md)
```

## Sources

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

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