# CVE-2020-15023: Weak cryptography in n/a

> Weak Diffie-Hellman randomness in Askey AP5100W allows offline brute-force of WPS PIN, enabling Wi-Fi network access.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 11 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c8j2-m9gv-4p68

## What is CVE-2020-15023?

CVE-2020-15023 is a medium-severity vulnerability in n/a, published on 11 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Askey AP5100W devices through AP5100W_Dual_SIG_1.01.097 are affected by WPS PIN offline brute-force cracking. This arises because of issues with the random number selection for the Diffie-Hellman exchange. By capturing an attempted (and even failed) WPS authentication attempt, it is possible to brute force the overall authentication exchange. This allows an attacker to obtain the recovered WPS PIN in minutes or even seconds, and eventually obtain the Wi-Fi PSK key, gaining access to the Wi=Fi network.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2020-15023?

It affects 1 product.


Products: Askey Ap5100w Firmware.

## How do I fix CVE-2020-15023?

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

## Is CVE-2020-15023 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15357](https://insights.sbomify.com/CVE-2020-15357/): Command injection in n/a (critical 9.8)
- [CVE-2020-26201](https://insights.sbomify.com/CVE-2020-26201/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15023 and fix it if it is affected.

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

## Sources

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

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