CVE-2020-0558
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper buffer restrictions in kernel mode driver for Intel(R) PROSet/Wireless WiFi products before version 21.70 on Windows 10 may allow an unprivileged user to potentially enable denial of service via adjacent access.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceImproper buffer restrictions in the kernel mode driver for Intel PROSet/Wireless WiFi products allow an unprivileged user to potentially cause a denial of service via adjacent network access. The vulnerability exists in versions prior to 21.70 on Windows 10, where insufficient bounds checking in the wireless driver could lead to a system crash or service disruption.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 21.70.0.6< 20.70.16.4< 19.51.27.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Intel PROSet/Wireless WiFi is installedOpen Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for entries containing 'Intel PROSet' or 'Intel Wireless'.Affected if The software is not present on the system.
-
Check Intel wireless driver versionOpen Device Manager > Network adapters > Intel WiFi adapter > Driver tab. Note the Driver Version displayed. Alternatively, run 'driverquery /v | findstr -i intel' in Command Prompt to list Intel driver versions.Affected if The displayed driver version is lower than 21.70.0.6, 20.70.16.4, or 19.51.27.1.
-
Confirm Windows 10 is in useRun 'winver' in Command Prompt or check System Properties. The vulnerability disclosure specifically targets Windows 10.Affected if The system is running Windows 10 and the driver version is in the vulnerable range.
-
Verify the kernel mode wireless driver is loadedRun 'sc query winmac' in Command Prompt or check Device Manager that the Intel wireless adapter shows as 'This device is working properly' under Device Status.Affected if The Intel wireless adapter driver is active and the version is vulnerable.
A system is affected if it runs Windows 10 with Intel PROSet/Wireless WiFi software installed and the driver version is below 21.70.0.6, 20.70.16.4, or 19.51.27.1.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data19.51.27.120.70.16.421.70.0.6
Update Intel PROSet/Wireless WiFi software to version 21.70 or later to obtain the patched kernel mode driver with proper buffer restrictions.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-0558 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data