AMD: CVE-2023-20569 Return Address Predictor
🔗 CVE IDs covered (1)
📋 Description
Why is this AMD CVE included in the Security Update Guide? The vulnerability assigned to this CVE is in certain processor models offered by AMD. The mitigation for this vulnerability requires a Windows update. This CVE is being documented in the Security Update Guide to announce that the latest builds of Windows enable the mitigation and provide protection against the vulnerability. Please see the following for more information: AMD-SB-7005
Are any additional steps required to protect my system after installing the August Windows updates? Customers who allow untrusted users to execute arbitrary code might wish to implement some extra security features within their systems. These features protect against the intra-process disclosure vectors that this speculative execution vulnerability describes. See the following for more information. Microsoft Windows client customers: See Microsoft Knowledge Base Article 4073119. Microsoft Windows Server/Azure Stack HCI customers: See Microsoft Knowledge Base Article 4072698 for additional information, including workarounds. Microsoft Azure has taken steps to address the security vulnerabilities at the hypervisor level to protect VMs running in Azure. More information can be found here. Can I expect any performance impact after I configure the registry keys? In some cases, installing these updates will have a performance impact. In testing Microsoft has seen some performance impact with these mitigations, in particular when hyperthreading is disabled. Microsoft values the security of its software and services and has made the decision to implement certain mitigation strategies in an effort to better secure our products. In some cases, mitigations are not enabled by default to allow users and administrators to evaluate the performance impact and risk exposure before deciding to enable the mitigations. We continue to work with hardware vendors to improve performance while maintaining a high level of security. Are Microsoft Azure assets protected? Microsoft is in the process of deploying mitigations across our cloud services and we expect this work to be complete soon. More information is available here. How do I know if I am affected? Please refer to AMD advisory AMD-SB-7005 to determine which AMD CPUs are affected.
How does this vulnerability affect Azure? This vulnerability affected a limited set of Azure Virtual Machine offerings using certain AMD EPYC processors. An update is being deployed across Azure infrastructure and the majority of customers are secured in the process automatically. Most customers do not need to take any action.
Is there any action Azure customers need to take? The majority of Azure customers are mitigated automatically by the update deployed across Azure and do not need to take any action. However, a small subset of customers with custom Maintenance Configurations on their Azure Virtual Machines may need to take action to apply the update. These customers will receive additional messaging through the Azure Portal via Azure Service Health with additional guidance.
🎯 Affected products32
- Azure Virtual Machines
- Windows 10 Version 1607 for 32-bit Systems
- Windows 10 Version 1607 for x64-based Systems
- Windows 10 Version 1809 for 32-bit Systems
- Windows 10 Version 1809 for ARM64-based Systems
- Windows 10 Version 1809 for x64-based Systems
- Windows 10 Version 21H2 for 32-bit Systems
- Windows 10 Version 21H2 for ARM64-based Systems
- Windows 10 Version 21H2 for x64-based Systems
- Windows 10 Version 22H2 for 32-bit Systems
- Windows 10 Version 22H2 for ARM64-based Systems
- Windows 10 Version 22H2 for x64-based Systems
- Windows 11 Version 22H2 for ARM64-based Systems
- Windows 11 Version 22H2 for x64-based Systems
- Windows 11 version 21H2 for ARM64-based Systems
- Windows 11 version 21H2 for x64-based Systems
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2008 for 32-bit Systems Service Pack 2
- Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
- Windows Server 2008 for x64-based Systems Service Pack 2
- Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
- Windows Server 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2012 R2 (Server Core installation)
- Windows Server 2016
- Windows Server 2016 (Server Core installation)
- Windows Server 2019
- Windows Server 2019 (Server Core installation)
- +2 more not shown
✅ Remediation
KB5029247 (Security Update) — fixed build 10.0.17763.4737 KB5029250 (Security Update) — fixed build 10.0.20348.1906 KB5029367 (Security Hotpatch Update) — fixed build 10.0.20348.1903 KB5029253 (Security Update) — fixed build 10.0.22000.2295 KB5029244 (Security Update) — fixed build 10.0.19044.3324 KB5029263 (Security Update) — fixed build 10.0.22621.2134 KB5029244 (Security Update) — fixed build 10.0.19045.3324 KBRelease Notes (Security Update) KB5029242 (Security Update) — fixed build 10.0.14393.6167 KB5029318 (Monthly Rollup) — fixed build 6.0.6003.22216 KB5029301 (Security Only) — fixed build 6.0.6003.22216 KB5029296 (Monthly Rollup) — fixed build 6.1.7601.26664 KB5029307 (Security Only) — fixed build 6.1.7601.26664 KB5029295 (Monthly Rollup) — fixed build 6.2.9200.24414 KB5029308 (Security Only) — fixed build 6.2.9200.24414 KB5029312 (Monthly Rollup) — fixed build 6.3.9600.21503 KB5029304 (Security Only) — fixed build 6.3.9600.21503
🔗 References (32)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-20569
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029247
- referencehttps://support.microsoft.com/help/5029247
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029250
- referencehttps://support.microsoft.com/help/5029250
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029367
- referencehttps://support.microsoft.com/help/5029367
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029253
- referencehttps://support.microsoft.com/help/5029253
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029244
- referencehttps://support.microsoft.com/help/5029244
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029263
- referencehttps://support.microsoft.com/help/5029263
- patchhttps://learn.microsoft.com/en-us/azure/virtual-machines/updates-maintenance-overview
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029242
- referencehttps://support.microsoft.com/help/5029242
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029318
- referencehttps://support.microsoft.com/help/5029318
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029301
- referencehttps://support.microsoft.com/help/5029301
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029296
- referencehttps://support.microsoft.com/help/5029296
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029307
- referencehttps://support.microsoft.com/help/5029307
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029295
- referencehttps://support.microsoft.com/help/5029295
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029308
- referencehttps://support.microsoft.com/help/5029308
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029312
- referencehttps://support.microsoft.com/help/5029312
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5029304
- referencehttps://support.microsoft.com/help/5029304