# CVE-2020-0569: Memory corruption in Intel(R) PROSet/Wireless WiFi products on Windows 10

> An authenticated local attacker can cause a denial of service via an out-of-bounds write in Intel PROSet/Wireless WiFi drivers.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2020-0569, DLA-2092-1, GHSA-jmp3-vh9c-94m8, SUSE-SU-2020:0346-1, SUSE-SU-2020:0349-1, UBUNTU-CVE-2020-0569, openSUSE-SU-2020:0209-1

## What is CVE-2020-0569?

CVE-2020-0569 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 23 Nov 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Out of bounds write in Intel(R) PROSet/Wireless WiFi products on Windows 10 may allow an authenticated user to potentially enable denial of service via local access.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 15 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libqt5-qtbase` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 5.9.4-8.21.2 |
| `libqt5-qtbase` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 5.9.4-8.21.2 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Module for Basesystem 15 | All versions | 5.9.4-8.21.2 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Module for Basesystem 15 SP1 | All versions | 5.9.7-13.5.1 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Module for Desktop Applications 15 | All versions | 5.9.4-8.21.2 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Module for Desktop Applications 15 SP1 | All versions | 5.9.7-13.5.1 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 5.9.4-8.21.2 |
| `libqt5-qtbase` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 5.9.4-8.21.2 |
| `libqt5-qtbase` | openSUSE:Leap 15.1 | All versions | 5.9.7-lp151.4.3.1 |

Products: Canonical Ubuntu Linux, Debian Debian Linux, Intel 7265 Firmware, Intel Ac 3165 Firmware, Intel Ac 3168 Firmware, Intel Ac 8260 Firmware, Intel Ac 8265 Firmware, Intel Ac 9260 Firmware, Intel Ac 9461 Firmware, Intel Ac 9462 Firmware, Intel Ac 9560 Firmware, Intel Ax200 Firmware, Intel Ax201 Firmware, Opensuse Leap, Qt Qt.

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

Apply the vendor's patch.

## Is CVE-2020-0569 being exploited?

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

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-0569 is a medium-severity memory corruption vulnerability in Canonical Ubuntu Linux, published on 23 Nov 2020. 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-2020-0569 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. 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-0569/ (Markdown: https://insights.sbomify.com/CVE-2020-0569/index.md)
```

## Sources

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

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