CVE-2025-20618
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 · uneditedStack-based buffer overflow for some Intel(R) PROSet/Wireless WiFi Software for Windows before version 23.100 may allow a privileged user to potentially enable denial of service via local 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 confidenceA stack-based buffer overflow vulnerability exists in Intel PROSet/Wireless WiFi Software for Windows in versions prior to 23.100. An authenticated, privileged user with local system access can trigger the overflow, potentially causing a denial-of-service condition.
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< 23.100.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:H/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.
-
Locate Intel PROSet/Wireless WiFi Software installationOpen Windows Control Panel > Programs and Features, or use PowerShell: Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like '*Intel*PROSet*' -or $_.Name -like '*Intel*Wireless*'} | Select-Object Name, VersionAffected if The software appears in installed programs with a version number below 23.100.0
-
Identify the exact version numberIn Programs and Features, locate 'Intel PROSet Wireless Software' or similar entry and note the Version column. If using PowerShell above, the Version property will display the full version stringAffected if Version number displayed is less than 23.100.0 (for example, 22.x.x, 21.x.x, etc.)
-
Verify via Intel driver utility if availableOpen Intel Driver & Support Assistant (if installed) or check Device Manager > Network Adapters > Intel WiFi adapter > Driver tab to view driver package versionAffected if The driver package or PROSet component version shown is below 23.100.0
-
Confirm privileged access contextReview system access controls and determine whether untrusted local users have privileged (administrator or system-level) access to the machineAffected if Untrusted or low-privilege users have administrative or system-level access, as the vulnerability requires authenticated privileged local access to trigger
A user is affected if Intel PROSet/Wireless WiFi Software version is installed and is below 23.100.0, and the system allows untrusted privileged local access.
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.
dbcve · scoped23.100.0
Upgrade Intel PROSet/Wireless WiFi Software to version 23.100 or later. Since this requires local privileged access, ensure systems are not exposed to untrusted local users and apply least-privilege principles.
Intel PROSet/Wireless WiFi Software version 23.100.0 or later
- 1. Identify the current Intel PROSet/Wireless WiFi Software version by opening Device Manager, expanding Network adapters, right-clicking the Intel wireless adapter, and selecting Properties > Driver tab
- 2. Navigate to the official Intel support download page for Intel PROSet/Wireless WiFi Software
- 3. Download Intel PROSet/Wireless WiFi Software version 23.100.0 or later for your specific adapter and Windows version
- 4. Close all applications and disconnect from any active VPN or network drives before installation
- 5. Run the downloaded installer as an Administrator
- 6. Follow the on-screen installation wizard prompts and restart the computer when prompted
- 7. After restart, verify the installed version matches or exceeds 23.100.0 via Device Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20618 — 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-2025-20618 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