描述:
Microsoft 發布了安全性更新,以應對影響數個 Microsoft 產品或元件的多個漏洞。有關安全性更新的列表,請參考以下網址:
https://msrc.microsoft.com/update-guide/releaseNote/2022-Oct
有報告指一個 Microsoft Windows 及 Server 中的權限提升漏洞 (CVE-2022-41033) 正受到攻擊,而另一個 Microsoft Office 中的泄漏資訊漏洞 (CVE-2022-41043) 技術詳情已被公開。系統管理員應立即為受影響的系統安裝修補程式,以減低受到網絡攻擊的風險。
受影響的系統:
- Microsoft Windows 7, 8.1, RT 8.1, 10, 11
- Microsoft Windows Server 2008, 2008 R2, 2012, 2012 R2, 2016, 2019, 2022
- Microsoft Office 2013, 2013 RT, 2016, 2019, 2019 for Mac, LTSC 2021, LTSC for Mac 2021
- Microsoft 365 Apps for Enterprise
- Microsoft SharePoint Foundation 2013
- Microsoft SharePoint Enterprise Server 2013, 2016
- Microsoft SharePoint Server 2019, Subscription Edition
- Microsoft Visual Studio 2019, 2022
- Visual Studio 2022 for Mac version 17.3
- Visual Studio Code
- .NET 6.0
- .NET Core 3.1
- Azure Arc-enabled Kubernetes cluster 1.5.8, 1.6.19, 1.7.18, 1.8.11
- Azure Service Fabric Explorer
- Azure Stack Edge
- Azure StorSimple 8000 Series
- Microsoft Malware Protection Engine
- Jupyter Extension for Visual Studio Code
影響:
成功利用這些漏洞可以導致遠端執行程式碼、權限提升、泄漏資訊、服務被拒絕、繞過保安功能及仿冒詐騙,視乎攻擊者利用哪個漏洞而定。
建議:
受影響產品的修補程式可在 Windows Update 或 Microsoft Update Catalog 獲取。受影響系統的用戶應遵從產品供應商的建議,立即採取行動以降低風險。
進一步資訊:
- https://msrc.microsoft.com/update-guide/releaseNote/2022-Oct
- https://www.hkcert.org/tc/security-bulletin/microsoft-monthly-security-update-october-2022
- https://www.cisa.gov/uscert/ncas/current-activity/2022/10/11/microsoft-releases-october-2022-security-updates
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-22035
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24504
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30198
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33634 (to CVE-2022-33635)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33645
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34689
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35770
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35829
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37965
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37968
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37970 (to CVE-2022-37971)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37973 (to CVE-2022-37991)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37993 (to CVE-2022-38001)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38003
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38016 (to CVE-2022-38017)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38021 (to CVE-2022-38022)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38025 (to CVE-2022-38034)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38036 (to CVE-2022-38051)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38053
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41031 (to CVE-2022-41034)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41036 (to CVE-2022-41038)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41042 (to CVE-2022-41043)
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41081
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-41083