{"id":206864,"date":"2018-07-20T17:18:59","date_gmt":"2018-07-20T15:18:59","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=206864"},"modified":"2022-08-22T10:12:18","modified_gmt":"2022-08-22T08:12:18","slug":"aktualisierte-microsoft-security-advisory-informationen","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2018\/07\/20\/aktualisierte-microsoft-security-advisory-informationen\/","title":{"rendered":"Aktualisierte Microsoft Security Advisory-Informationen"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2015\/01\/Schutz.jpg\" width=\"40\" align=\"left\" height=\"47\"\/>Microsoft hat am 19. Juli 2018 einige Sicherheitsinformationen (Microsoft Security Advisory Notification) \u00fcberarbeitet. Zudem gab es Revisionen bei den Beschreibungen der Sicherheitsupdates. Hier ein \u00dcberblick, was sich ge\u00e4ndert hat. <\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/ssl-vg03.met.vgwort.de\/na\/55c852fc50e64698baf8223974158380\" width=\"1\" height=\"1\"\/>********************************************************************<br \/>Title: Microsoft Security Advisory Notification<br \/>Issued: July 19, 2018<br \/>********************************************************************<br \/>Security Advisories Released or Updated on July 19, 2018<br \/>===================================================================<\/p>\n<p>* Microsoft Security Advisory ADV180002<\/p>\n<p>&#8211; Title: Guidance to mitigate speculative execution side-channel<br \/>&nbsp;&nbsp; vulnerabilities<br \/>&#8211; <a href=\"https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\/&nbsp;&nbsp;&nbsp;&nbsp; advisory\/ADV180002\" target=\"_blank\" rel=\"noopener\">https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\/<br \/>&nbsp;&nbsp;&nbsp;&nbsp; advisory\/ADV180002<\/a><br \/>&#8211; Reason for Revision: To address a known issue in the security<br \/>&nbsp;&nbsp; updates released on July 10, Microsoft is releasing Alternate<br \/>&nbsp;&nbsp; Cumulative update packages for Windows 10, and Standalone and<br \/>&nbsp;&nbsp; Preview Rollup packages for all other supported editions of<br \/>&nbsp;&nbsp; Windows. These packages are available via Microsoft Update<br \/>&nbsp;&nbsp; catalog, WSUS, or by manually searching Windows Update. Customers<br \/>&nbsp;&nbsp; who are experiencing issues after installing the July Windows<br \/>&nbsp;&nbsp; security updates should install the replacement packages as<br \/>&nbsp;&nbsp; applicable. Please refer to the Affected Products table for the<br \/>&nbsp;&nbsp; replacement package KB numbers. Customers who have successfully<br \/>&nbsp;&nbsp; installed the security updates and who are not experiencing any<br \/>&nbsp;&nbsp; issues do not need to take any action. <br \/>&#8211; Originally posted: January 3, 2018<br \/>&#8211; Updated: July 19, 2018<br \/>&#8211; Version: 22.0<\/p>\n<p>* Microsoft Security Advisory ADV180016<\/p>\n<p>&#8211; Title: Microsoft Guidance for Lazy FP State Restore<br \/>&#8211; <a href=\"https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\/&nbsp;&nbsp;&nbsp;&nbsp;advisory\/ADV180016\" target=\"_blank\" rel=\"noopener\">https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\/<br \/>&nbsp;&nbsp;&nbsp; advisory\/ADV180016<\/a><br \/>&#8211; Reason for Revision: To address a known issue in the security<br \/>&nbsp;&nbsp; updates released on July 10, Microsoft is releasing Alternate<br \/>&nbsp;&nbsp; Cumulative update packages for Windows 10, and Standalone and<br \/>&nbsp;&nbsp; Preview Rollup packages for all other supported editions of<br \/>&nbsp;&nbsp; Windows. These packages are available via Microsoft Update<br \/>&nbsp;&nbsp; catalog, WSUS, or by manually searching Windows Update. Customers<br \/>&nbsp;&nbsp; who are experiencing issues after installing the July Windows<br \/>&nbsp;&nbsp; security updates should install the replacement packages as<br \/>&nbsp;&nbsp; applicable. Please refer to the Affected Products table for the<br \/>&nbsp;&nbsp; replacement package KB numbers. Customers who have successfully<br \/>&nbsp;&nbsp; installed the security updates and who are not experiencing any<br \/>&nbsp;&nbsp; issues do not need to take any action. <br \/>&#8211; Originally posted: June 13, 2018<br \/>&#8211; Updated: July 19, 2018<br \/>&#8211; Version: 3.0<\/p>\n<p>********************************************************************<br \/>Title: Microsoft Security Update Releases<br \/>Issued: July 19, 2018<br \/>********************************************************************<\/p>\n<p>Summary<br \/>=======<\/p>\n<p>The following CVEs have undergone a major revision increment:<\/p>\n<p>* CVE-2018-8202<br \/>* CVE-2018-8260<br \/>* CVE-2018-8284<br \/>* CVE-2018-8356<br \/>&nbsp; <br \/>Revision Information:<br \/>=====================<\/p>\n<p>&#8211; <a href=\"https:\/\/web.archive.org\/web\/20201101051813\/https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\" target=\"_blank\" rel=\"noopener\">https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance<\/a><br \/>&#8211; Reason for Revision: To address a known issue in the security<br \/>&nbsp;&nbsp; updates released on July 10, Microsoft is releasing Cumulative<br \/>&nbsp;&nbsp; Update packages for all supported editions of Windows 10. These<br \/>&nbsp;&nbsp; packages are available via Microsoft Update catalog, WSUS, or by<br \/>&nbsp;&nbsp; manually searching Windows Update. Customers who are experiencing<br \/>&nbsp;&nbsp; issues after installing the July Windows security updates should<br \/>&nbsp;&nbsp; install the replacement packages as applicable. Note that the<br \/>&nbsp;&nbsp; Monthly Rollup and Security Only updates for .NET Framework are<br \/>&nbsp;&nbsp; not affected. Please refer to the Affected Products table for the<br \/>&nbsp;&nbsp; replacement package KB numbers. Customers who have successfully<br \/>&nbsp;&nbsp; installed the security updates and who are not experiencing any<br \/>&nbsp;&nbsp; issues do not need to take any action.<br \/>&#8211; Originally posted: July 10, 2018<br \/>&#8211; Updated: July 19, 2018<br \/>&#8211; Aggregate CVE Severity Rating: Important<br \/>&#8211; Version: 2.0<\/p>\n<p>The following CVEs have undergone a major revision increment:<\/p>\n<p>* CVE-2018-0949<br \/>* CVE-2018-8242<br \/>* CVE-2018-8287<br \/>* CVE-2018-8288<br \/>* CVE-2018-8291<br \/>* CVE-2018-8296<\/p>\n<p>Revision Information:<br \/>=====================<\/p>\n<p>&#8211; <a href=\"https:\/\/web.archive.org\/web\/20201101051813\/https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\" target=\"_blank\" rel=\"noopener\">https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance<\/a><br \/>&#8211; Reason for Revision: To address a known issue in the security<br \/>&nbsp;&nbsp; updates released on July 10, Microsoft is releasing Cumulative<br \/>&nbsp;&nbsp; Update packages for Windows 10, and Standalone and Preview Rollup<br \/>&nbsp;&nbsp; packages for all other supported editions of Windows. These packages<br \/>&nbsp;&nbsp; are available via Microsoft Update catalog, WSUS, or by manually<br \/>&nbsp;&nbsp; searching Windows Update. Customers who are experiencing issues<br \/>&nbsp;&nbsp; after installing the July Windows security updates should install<br \/>&nbsp;&nbsp; the replacement packages as applicable. Note that the IE Cumulative<br \/>&nbsp;&nbsp; updates are not affected. Please refer to the Affected Products<br \/>&nbsp;&nbsp; table for the replacement package KB numbers. Customers who have<br \/>&nbsp;&nbsp; successfully installed the security updates and who are not<br \/>&nbsp;&nbsp; experiencing any issues do not need to take any action.<br \/>&#8211; Originally posted: July 10, 2018<br \/>&#8211; Updated: July 19, 2018<br \/>&#8211; Aggregate CVE Severity Rating: Important<br \/>&#8211; Version: 2.0<\/p>\n<p>The following CVEs have undergone a major revision increment:<\/p>\n<p>* CVE-2018-8125&nbsp;&nbsp;&nbsp; * CVE-2018-8279&nbsp;&nbsp;&nbsp; * CVE-2018-8301<br \/>* CVE-2018-8206&nbsp;&nbsp;&nbsp; * CVE-2018-8280&nbsp;&nbsp;&nbsp; * CVE-2018-8304<br \/>* CVE-2018-8222&nbsp;&nbsp;&nbsp; * CVE-2018-8282&nbsp;&nbsp;&nbsp; * CVE-2018-8307<br \/>* CVE-2018-8262&nbsp;&nbsp;&nbsp; * CVE-2018-8286&nbsp;&nbsp;&nbsp; * CVE-2018-8308<br \/>* CVE-2018-8274&nbsp;&nbsp;&nbsp; * CVE-2018-8289&nbsp;&nbsp;&nbsp; * CVE-2018-8309<br \/>* CVE-2018-8275&nbsp;&nbsp;&nbsp; * CVE-2018-8290&nbsp;&nbsp;&nbsp; * CVE-2018-8313<br \/>* CVE-2018-8276&nbsp;&nbsp;&nbsp; * CVE-2018-8294&nbsp;&nbsp;&nbsp; * CVE-2018-8314<br \/>* CVE-2018-8278&nbsp;&nbsp;&nbsp; * CVE-2018-8297&nbsp;&nbsp;&nbsp; * CVE-2018-8324<br \/>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * CVE-2018-8325<\/p>\n<p>Revision Information:<br \/>=====================<\/p>\n<p>&#8211; <a href=\"https:\/\/web.archive.org\/web\/20201101051813\/https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\" target=\"_blank\" rel=\"noopener\">https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance<\/a><br \/>&#8211; Reason for Revision: To address a known issue in the security<br \/>&nbsp;&nbsp; updates released on July 10, Microsoft is releasing Cumulative<br \/>&nbsp;&nbsp; Update packages for Windows 10, and Standalone and Preview Rollup<br \/>&nbsp;&nbsp; packages for all other supported editions of Windows. These<br \/>&nbsp;&nbsp; packages are available via Microsoft Update catalog, WSUS, or by<br \/>&nbsp;&nbsp; manually searching Windows Update. Customers who are experiencing<br \/>&nbsp;&nbsp; issues after installing the July Windows security updates should<br \/>&nbsp;&nbsp; install the replacement packages as applicable. Please refer to the<br \/>&nbsp;&nbsp; Affected Products table for the replacement package KB numbers.<br \/>&nbsp;&nbsp; Customers who have successfully installed the security updates and<br \/>&nbsp;&nbsp; who are not experiencing any issues do not need to take any action.<br \/>&#8211; Originally posted: July 10, 2018<br \/>&#8211; Updated: July 19, 2018<br \/>&#8211; Aggregate CVE Severity Rating: Critical<br \/>&#8211; Version: 2.0<\/p>\n<p>The following CVE has undergone a major revision increment:<\/p>\n<p>* CVE-2018-8356<\/p>\n<p>Revision Information:<br \/>=====================<\/p>\n<p>&#8211; <a href=\"https:\/\/web.archive.org\/web\/20201101051813\/https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance\" target=\"_blank\" rel=\"noopener\">https:\/\/portal.msrc.microsoft.com\/en-us\/security-guidance<\/a><br \/>&#8211; Reason for Revision: Revised the Affected Products table to<br \/>&nbsp;&nbsp; include PowerShell Core 6.0 and PowerShell Core 6.1 because<br \/>&nbsp;&nbsp; these products are affected by CVE-2018-9356. See <br \/>&nbsp;&nbsp; <a href=\"https:\/\/github.com\/PowerShell\/Announcements\/issues\/6\" target=\"_blank\" rel=\"noopener\">https:\/\/github.com\/PowerShell\/Announcements\/issues\/6<\/a> for <br \/>&nbsp;&nbsp; more information.<br \/>&#8211; Originally posted: July 10, 2018<br \/>&#8211; Updated: July 19, 2018<br \/>&#8211; Aggregate CVE Severity Rating: Important<br \/>&#8211; Version: 3.0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft hat am 19. Juli 2018 einige Sicherheitsinformationen (Microsoft Security Advisory Notification) \u00fcberarbeitet. Zudem gab es Revisionen bei den Beschreibungen der Sicherheitsupdates. Hier ein \u00dcberblick, was sich ge\u00e4ndert hat.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[426],"tags":[4328],"class_list":["post-206864","post","type-post","status-publish","format-standard","hentry","category-sicherheit","tag-sicherheit"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/206864","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/comments?post=206864"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/206864\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=206864"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=206864"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=206864"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}