# CVE-2011-4507: Weak cryptography in n/a

> Remote attackers can bypass authentication or read sensitive data on D-Link DIR-685 routers using specific WPA/WPA2 configurations during high traffic.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4pvf-3j35-325v

## What is CVE-2011-4507?

CVE-2011-4507 is a high-severity vulnerability in n/a, published on 22 Nov 2011. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The D-Link DIR-685 router, when certain WPA and WPA2 configurations are used, does not maintain an encrypted wireless network during transfer of a large amount of network traffic, which allows remote attackers to obtain sensitive information or bypass authentication via a Wi-Fi device.

Weakness: CWE-310

## Which versions are affected by CVE-2011-4507?

It affects 1 product.


Products: Dlink Dir-685.

## How do I fix CVE-2011-4507?

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

## Is CVE-2011-4507 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4507 and fix it if it is affected.

What it is: CVE-2011-4507 is a high-severity vulnerability in n/a, published on 22 Nov 2011. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-4507 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-2011-4507/ (Markdown: https://insights.sbomify.com/CVE-2011-4507/index.md)
```

## Sources

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

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