← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2018-8589 exploited? Yes: in CISA KEV since 23 May 2022

Gociux · Microsoft Win32k · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2018-8589, Microsoft Win32k Privilege Escalation Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 23 May 2022, 1286 days after it was published. It affects Microsoft Win32k. If you run it, CISA's required action is: Apply updates per vendor instructions.

exploitedYesCISA KEV · 23 May 2022
ransomwareNot knownno confirmed use
EPSSbelow top 10%lower predicted activity right now (it is still confirmed exploited)
severity7.8CVSS 3.1 · high
US federal due13 Jun 2022BOD 22-01 deadline

What it is

A privilege escalation vulnerability exists when Windows improperly handles calls to Win32k.sys. An attacker who successfully exploited this vulnerability could run remote code in the security context of the local system.

VendorMicrosoft (391 exploited CVEs in KEV)
ProductWin32k
VulnerabilityMicrosoft Win32k Privilege Escalation Vulnerability
Weaknessnot specified
Published14 Nov 2018
Added to KEV23 May 2022
Reported by (CNA)microsoft

What to do

  1. Check whether you run it. Look for Win32k in your asset inventory, including appliances and cloud images. Stack check lists every exploited Microsoft CVE at once.
  2. Apply the fix. Apply updates per vendor instructions.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 14 Nov 2018.
  4. Get told next time. Email alerts when CISA adds a CVE for Microsoft.

Other exploited CVEs in Win32k

References

Questions

Is CVE-2018-8589 being exploited?

Yes. CISA added CVE-2018-8589 to the Known Exploited Vulnerabilities catalog on 23 May 2022, which means there is reliable evidence of exploitation in the wild.

Is CVE-2018-8589 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2018-8589?

Apply updates per vendor instructions. Check Microsoft's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Win32k and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in May 2022 · Microsoft scorecard · act-now radar.

Running Microsoft in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →