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

> Remote attackers can bypass Wi-Fi authentication by deriving the WPS PIN from broadcast MAC addresses, granting unauthorized network access.

- **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:** 31 Dec 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-2c7m-mmf4-jwf3

## What is CVE-2012-6371?

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

### Official description

The WPA2 implementation on the Belkin N900 F9K1104v1 router establishes a WPS PIN based on 6 digits of the LAN/WLAN MAC address, which makes it easier for remote attackers to obtain access to a Wi-Fi network by reading broadcast packets, a different vulnerability than CVE-2012-4366.

Weakness: CWE-310

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

It affects 1 product.


Products: Belkin N900 Wireless Router.

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

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

## Is CVE-2012-6371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6371 is a low-severity vulnerability in n/a, published on 31 Dec 2012. 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-2012-6371 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-2012-6371/ (Markdown: https://insights.sbomify.com/CVE-2012-6371/index.md)
```

## Sources

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

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