Proset\/wireless WifiApplication · Intel

CVE-2025-20062

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-13
Fix available
A fix is available. Upgrade to 23.100.0 or later.
See remediation →
66/100
Remediation priority · Elevated
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 · high confidence

A use-after-free vulnerability exists in Intel PROSet/Wireless WiFi Software for Windows versions prior to 23.100. An unauthenticated attacker with adjacent network access can potentially trigger this memory corruption flaw, leading to denial of service.

MitigationUpdate Intel PROSet/Wireless WiFi Software to 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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:H/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. Locate Intel PROSet/Wireless WiFi Software in installed programs
    Open Control Panel > Programs and Features (or Settings > Apps > Installed apps on Windows 10/11), then search for 'Intel PROSet' or 'Intel Wireless' in the list of installed software
    Affected if The software appears in the list with a version number lower than 23.100.0
  2. Check the software version via Windows Registry
    Open Registry Editor (regedit.exe), navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Intel\Wireless, and look for a Version or DisplayVersion value
    Affected if The registry value shows a version lower than 23.100.0 or the key does not exist (indicating the software may not be installed or a different version scheme is used)
  3. Check the Intel wireless adapter driver version
    Open Device Manager, expand Network adapters, right-click the Intel wireless adapter, select Properties, go to the Driver tab, and note the Driver Version
    Affected if The driver version corresponds to an Intel PROSet/Wireless software package older than version 23.100
  4. Inspect the Intel Wireless Common component file version
    Navigate to C:\Program Files\Intel\WiFi\ (or C:\Program Files (x86)\Intel\WiFi\), locate the common Intel wireless DLL files, right-click and view Properties > Details to check the File Version
    Affected if The file version of the Intel wireless components is below 23.100.0.0

The system is affected if Intel PROSet/Wireless WiFi Software or its components are installed with a version number lower than 23.100.0 on Windows.

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

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

Recommended fix High confidence

Intel PROSet/Wireless WiFi Software version 23.100.0 or later

  1. Check the current version of Intel PROSet/Wireless WiFi Software installed on the system via Programs and Features or Device Manager
  2. Download Intel PROSet/Wireless WiFi Software version 23.100.0 or later from the official Intel download center
  3. Install the updated version following the on-screen prompts
  4. Restart the system to ensure the new driver and software components are properly loaded
  5. Verify the installed version is 23.100.0 or later

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

Fix this in Proset\/wireless Wifi Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20062 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20062 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