# CVE-2012-4366: Weak cryptography in n/a

> Attackers can predict default WPA2 passwords from MAC addresses to gain unauthorized network access on Belkin routers.

- **Severity:** Low 3.3 (`AV:A/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** 20 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f446-wm48-q9x7

## What is CVE-2012-4366?

CVE-2012-4366 is a low-severity vulnerability in n/a, published on 20 Nov 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Belkin wireless routers Surf N150 Model F7D1301v1, N900 Model F9K1104v1, N450 Model F9K1105V2, and N300 Model F7D2301v1 generate a predictable default WPA2-PSK passphrase based on eight digits of the WAN MAC address, which allows remote attackers to access the network by sniffing the beacon frames.

Weakness: CWE-310

## Which versions are affected by CVE-2012-4366?

It affects 4 products.


Products: Belkin N150 Wireless Router, Belkin N300 Wireless Router, Belkin N450 Wireless Router, Belkin N900 Wireless Router.

## How do I fix CVE-2012-4366?

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

## Is CVE-2012-4366 being exploited?

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

Public exploit code:

- Belkin Wireless Router - Default WPS PIN Security (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4366 and fix it if it is affected.

What it is: CVE-2012-4366 is a low-severity vulnerability in n/a, published on 20 Nov 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4366 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-2012-4366/ (Markdown: https://insights.sbomify.com/CVE-2012-4366/index.md)
```

## Sources

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

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