CVE Tools
Track your stack

CVE-2018-8405

Exploited in the wild. In CISA KEV since 2022‑03‑28. A vendor fix is available.

CVSS 3.17.8HighEPSS percentile89th3.4% chance in 30 daysCISA KEVListedsince 2022-03-28, due 2022-04-18
No public exploit knownFixVendor fixNo build named by the sources

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

  • Microsoft Windows Server 2012 R2Affected: (Server Core installation)Upgrade to: not statedStated by: CVE record
  • Microsoft Windows RT 8.1Affected: Windows RT 8.1Upgrade to: not statedStated by: CVE record
  • Microsoft Windows Server 2016Affected: (Server Core installation)Upgrade to: not statedStated by: CVE record
  • Microsoft Windows 8.1Affected: 32-bit systemsUpgrade to: not statedAffected: x64-based systemsUpgrade to: not statedStated by: CVE record
  • Microsoft Windows 10Affected: 32-bit SystemsUpgrade to: not statedAffected: Version 1607 for 32-bit SystemsUpgrade to: not statedAffected: Version 1607 for x64-based SystemsUpgrade to: not statedAffected: Version 1703 for 32-bit SystemsUpgrade to: not stated + 6 more branchesStated by: CVE record

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

Coverage timeline

0 publishers

  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened.

What it is

From the CVE record

An elevation of privilege vulnerability exists when the DirectX Graphics Kernel (DXGKRNL) driver improperly handles objects in memory, aka "DirectX Graphics Kernel Elevation of Privilege Vulnerability." This affects Windows Server 2012 R2, Windows RT 8.1, Windows Server 2016, Windows 8.1, Windows 10, Windows 10 Servers. This CVE ID is unique from CVE-2018-8400, CVE-2018-8401, CVE-2018-8406.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS89th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2022-03-28.

US federal agencies must remediate by 2022-04-18.

Known use in ransomware campaigns.

Apply updates per vendor instructions.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

3.4% chance of exploitation activity in the next 30 days, which ranks it in the 89th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 2871 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changemoderate → low
  3. Patch availablerecord updated
  4. Added to CISA KEVransomware campaign
  5. Publishedweakness classified

Affected products

And 22 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

References in the record

And 4 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Microsoft, not every advisory. This one: actively exploited.