dbcve.org
Proset\/wireless WifiApplication · Intel

CVE-2025-20006

HIGH · 7.4 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 23.100.0 or later.
See remediation →
79/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Use after free for some Intel(R) PROSet/Wireless WiFi Software for Windows before version 23.100 may allow an unauthenticated 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 · moderate confidence

Use-after-free vulnerability in Intel PROSet/Wireless WiFi Software for Windows versions prior to 23.100 allows an unauthenticated attacker with adjacent network access to potentially cause denial of service by accessing memory that has been freed.

MitigationUpgrade to Intel PROSet/Wireless WiFi Software version 23.100 or later to address the vulnerability.

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
Proset\/wireless WifiApplication
Affected:< 23.100.0

CVSS 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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Intel PROSet/Wireless WiFi Software is installed
    Open Programs and Features (appwiz.cpl) and look for entries containing 'Intel PROSet' or 'Intel Wireless' in the name, or check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Intel wireless-related entries.
    Affected if No Intel PROSet/Wireless WiFi Software entry is found - the system is not affected because the vulnerable software is not installed.
  2. Locate the installed version number
    In Programs and Features, find the Intel PROSet/Wireless entry and note the version column. Alternatively, check the registry key HKLM\SOFTWARE\Intel\Proset\Wireless\CurrentVersion (or similar Intel wireless registry paths) for a Version or DisplayVersion value.
    Affected if Unable to determine the version - further investigation needed to confirm the installed version.
  3. Compare installed version against the vulnerable range
    Compare the version found (for example, 22.x.x, 23.x.x, etc.) to the threshold version 23.100.0. Versions prior to 23.100.0 (such as 23.50.0, 22.x.x, 21.x.x) are within the vulnerable range.
    Affected if The installed version is below 23.100.0 - the environment is affected by this vulnerability.
  4. Check the WiFi driver version as supplemental indicator
    Open Device Manager, expand Network adapters, right-click the Intel WiFi adapter and select Properties. Look at the Driver version field under the Driver tab. Intel PROSet and WiFi driver versions often correlate.
    Affected if The driver version suggests an older PROSet installation (below 23.100) - this corroborates potential exposure.

The system is affected if Intel PROSet/Wireless WiFi Software is installed with a version number less than 23.100.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 23.100.0 or later
Fixed in 23.100.0
Interim mitigation

Upgrade to Intel PROSet/Wireless WiFi Software version 23.100 or later to address the vulnerability.

Recommended fix High confidence

23.100.0 or later

  1. Open Windows Device Manager and expand the Network adapters section to identify the Intel wireless adapter and current driver version
  2. Alternatively, open Intel PROSet/Wireless Software from the system tray or Start menu and check the version information
  3. Download Intel PROSet/Wireless WiFi Software version 23.100.0 or later from Intel's official support website (intel.com/support)
  4. Run the installer and follow the on-screen prompts to upgrade the software
  5. Restart the computer when prompted to complete the installation
  6. Verify the updated version by checking the software or driver version again

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Proset\/wireless Wifi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20006 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20006 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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