| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| Windows TCP/IP Remote Code Execution Vulnerability |
| .NET Core and Visual Studio Denial of Service Vulnerability |
| Skype for Business and Lync Remote Code Execution Vulnerability |
| Skype for Business and Lync Spoofing Vulnerability |
| Microsoft SharePoint Server Remote Code Execution Vulnerability |
| Windows Overlay Filter Information Disclosure Vulnerability |
| Windows Hyper-V Denial of Service Vulnerability |
| Windows DCOM Server Security Feature Bypass |
| Windows Installer Spoofing Vulnerability |
| Microsoft Exchange Server Remote Code Execution Vulnerability |
| Insufficient validation of elliptic curve points in SEV-legacy firmware may compromise SEV-legacy guest migration potentially resulting in loss of guest's integrity or confidentiality. |
| LFENCE/JMP (mitigation V2-2) may not sufficiently mitigate CVE-2017-5715 on some AMD CPUs. |
| AMD processors may speculatively re-order load instructions which can result in stale data being observed when multiple processors are operating on shared memory, resulting in potential data leakage. |
| A malicious or compromised UApp or ABL may coerce the bootloader into corrupting arbitrary memory potentially leading to loss of integrity of data. |
| An attacker with root account privileges can load any legitimately signed firmware image into the Audio Co-Processor (ACP,) irrespective of the respective signing key being declared as usable for authenticating an ACP firmware image, potentially resulting in a denial of service. |
| Insufficient checks in System Management Unit (SMU) FeatureConfig may result in reenabling features potentially resulting in denial of resources and/or denial of service. |
| Insufficient General Purpose IO (GPIO) bounds check in System Management Unit (SMU) may result in access/updates from/to invalid address space that could result in denial of service. |
| An attacker, who gained elevated privileges via some other vulnerability, may be able to read data from Boot ROM resulting in a loss of system integrity. |
| A malicious or compromised UApp or ABL could potentially change the value that the ASP uses for its reserved DRAM, to one outside of the fenced area, potentially leading to data exposure. |
| A malicious or compromised UApp or ABL may be used by an attacker to issue a malformed system call which results in mapping sensitive System Management Network (SMN) registers leading to a loss of integrity and availability. |
