CVE-2015-2291
High 7.8KEV · exploitedPublic exploitFix status unknownIntel Ethernet Diagnostics Driver for Windows Denial-of-Service Vulnerability
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 97% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Passed 1359 days ago for U.S. federal agencies
Description
(1) IQVW32.sys before 1.3.1.0 and (2) IQVW64.sys before 1.3.1.0 in the Intel Ethernet diagnostics driver for Windows allows local users to cause a denial of service or possibly execute arbitrary code with kernel privileges via a crafted (a) 0x80862013, (b) 0x8086200B, (c) 0x8086200F, or (d) 0x80862007 IOCTL call.
Weakness: CWE-20
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- intel.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Intel | Ethernet Diagnostics Driver for Windows | Not documented | Not documented | CISA KEV |
Timeline
Disclosure
CVE record published by mitre
Source: CVE Program (opens in a new tab)
10 Feb 2023KEV
Added to the CISA Known Exploited Vulnerabilities catalog
Source: CISA KEV (opens in a new tab)
10 Feb 2023Exploitation
Exploitation confirmed by CISA KEV
Source: CISA KEV (opens in a new tab)
Vendor guidance and references
- https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00051.html (opens in a new tab)vendor-advisory
- 79623 (opens in a new tab)vdb-entry, x_refsource_bid, x_transferred
- https://nvd.nist.gov/vuln/detail/CVE-2015-2291 (opens in a new tab)government
- https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00051&languageid=en-fr (opens in a new tab)x_refsource_confirm, x_transferred
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2015-2291 (opens in a new tab)government-resource
Public exploit code
Exploit or proof-of-concept code is publicly available on Exploit-DB. Shown as a prioritization and defensive-testing signal — treat exploit code as hostile and run it only against systems you are authorized to test.