CVE-2020-0988: Critical severity windows 10 vulnerability

Published Apr 15, 2020

Updated

A remote code execution vulnerability exists when the Windows Jet Database Engine improperly handles objects in memory, aka 'Jet Database Engine Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2020-0889, CVE-2020-0953, CVE-2020-0959, CVE-2020-0960, CVE-2020-0992, CVE-2020-0994, CVE-2020-0995, CVE-2020-0999, CVE-2020-1008.

Affected Software

20 affected components

Microsoft Windows 10

Microsoft Windows 10=1607

Microsoft Windows 10=1709

Microsoft Windows 10=1803

Microsoft Windows 10=1809

Microsoft Windows 10=1903

Microsoft Windows 10=1909

Microsoft Windows 7=sp1

Microsoft Windows 8.1

Microsoft Windows RT 8.1

Microsoft Windows Server 2008=sp2

Microsoft Windows Server 2008=r2-sp1

Microsoft Windows Server 2012

Microsoft Windows Server 2012=r2

Microsoft Windows Server 2016

Microsoft Windows Server 2016=1803

Microsoft Windows Server 2016=1903

Microsoft Windows Server 2016=1909

Microsoft Windows Server 2019

Remediation

Patch Available

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0988

Event History

Apr 15, 2020

CVE Published

via MITRE·03:13 PM

Data Sourced

via MITRE·03:13 PM

DescriptionWeakness

Frequently Asked Questions

What is the severity of CVE-2020-0988?

CVE-2020-0988 has a severity rating of critical due to its potential for remote code execution.

How do I fix CVE-2020-0988?

To fix CVE-2020-0988, install the latest security updates provided by Microsoft for affected Windows versions.

Which Windows versions are affected by CVE-2020-0988?

CVE-2020-0988 affects multiple Microsoft Windows versions, including Windows 7, 8.1, 10, and various Windows Server editions.

What impact does CVE-2020-0988 have on affected systems?

CVE-2020-0988 can allow an attacker to run arbitrary code on affected systems, potentially leading to full system control.

Is there a workaround for CVE-2020-0988?

While a patch is the recommended solution for CVE-2020-0988, there is no official workaround provided by Microsoft.