Proset\/wireless WifiApplication · Intel

CVE-2019-11156

HIGH · 7.8 CVSS v3.1 Published 2019-11-14
Fix available
A fix is available. Upgrade to 21.40 or later.
See remediation →
80/100
Remediation priority · High
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
Logic errors in Intel(R) PROSet/Wireless WiFi Software before version 21.40 may allow an authenticated user to potentially enable escalation of privilege, denial of service, and information disclosure 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 confidence

Logic errors in Intel(R) PROSet/Wireless WiFi Software before version 21.40 allow an authenticated user with local access to potentially escalate privileges, cause denial of service, or obtain information disclosure through the vulnerable wireless driver component.

MitigationUpgrade Intel PROSet/Wireless WiFi Software to version 21.40 or later to address the logic errors; apply via standard enterprise patch management or manual installation on affected endpoints.

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:< 21.40

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Verify Intel PROSet/Wireless WiFi Software is installed
    Check Windows Programs and Features or registry for Intel PROSet/Wireless WiFi Software entry, or look for Intel wireless utility in installed programs
    Affected if The software is not listed or no Intel wireless utility is found on the system, the system is not affected by this specific product vulnerability
  2. Identify installed Intel wireless software version
    Open the Intel PROSet/Wireless WiFi Software utility, typically accessible via system tray icon or Windows Start menu, and locate the version information in the About or Help section. Alternatively, check Add/Remove Programs for the version number displayed next to the Intel PROSet/Wireless entry
    Affected if The displayed version number is lower than 21.40 (for example, 21.30, 20.x, or earlier)
  3. Confirm wireless driver component is present
    Open Device Manager, expand Network adapters, and verify an Intel wireless adapter with its driver is installed and enabled. Additionally, confirm the Intel PROSet wireless utility service is running
    Affected if No Intel wireless adapter or driver is present and the Intel PROSet utility is not installed, the specific driver component affected by this CVE is not present
  4. Verify local user access context
    Check whether standard user accounts exist on the system. This vulnerability requires an authenticated local user to exploit, so systems without additional local users (single-user home systems) have reduced attack surface, though the software flaw still exists if version is vulnerable
    Affected if The installed version is below 21.40 AND the system has multiple user accounts or allows local account access, making the privilege escalation vector applicable

The system is affected if Intel PROSet/Wireless WiFi Software is installed with a version lower than 21.40 and the Intel wireless driver component is present on the system.

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.

From vendor data
Upgrade available Upgrade to 21.40 or later
Fixed in 21.40
Interim mitigation

Upgrade Intel PROSet/Wireless WiFi Software to version 21.40 or later to address the logic errors; apply via standard enterprise patch management or manual installation on affected endpoints.

Fix this in Proset\/wireless Wifi Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11156 — 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-2019-11156 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