# CVE-2016-4824: Auth bypass in n/a

> Remote attackers can brute-force WPS PINs to gain unauthorized network access due to missing attempt limits on Corega routers.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 25 Jun 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c28q-c5r3-37pq

## What is CVE-2016-4824?

CVE-2016-4824 is a medium-severity authentication bypass vulnerability in n/a, published on 25 Jun 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Wi-Fi Protected Setup (WPS) implementation on Corega CG-WLR300GNV and CG-WLR300GNV-W devices does not restrict the number of PIN authentication attempts, which makes it easier for remote attackers to obtain network access via a brute-force attack.

Weakness: CWE-254

## Which versions are affected by CVE-2016-4824?

It affects 2 products.


Products: Corega Cg-Wlr300gnv-W Firmware, Corega Cg-Wlr300gnv Firmware.

## How do I fix CVE-2016-4824?

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

## Is CVE-2016-4824 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-4824 and fix it if it is affected.

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

## Sources

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

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