{"id":27897,"date":"2022-12-06T06:55:19","date_gmt":"2022-12-06T05:55:19","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=27897"},"modified":"2022-12-06T06:55:19","modified_gmt":"2022-12-06T05:55:19","slug":"edge-108-0-1462-42","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/12\/06\/edge-108-0-1462-42\/","title":{"rendered":"Edge 108.0.1462.42"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" title=\"Edge\" src=\"https:\/\/www.borncity.com\/blog\/wp-content\/uploads\/2020\/01\/Edge.jpg\" alt=\"Edge\" width=\"65\" height=\"67\" align=\"left\" border=\"0\" \/>[<a href=\"https:\/\/www.borncity.com\/blog\/2022\/12\/06\/edge-108-0-1462-41-42-als-sicherheitsupdates\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Microsoft has raised the Edge browser in the Stable Channel and Extended Stable Channel to version 108.0.1462.42 on December 5, 2022. It is a new development branch (108 version) that also fixes vulnerabilities reported by the Chromium team and already exploited in the wild.<\/p>\n<p><!--more--><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg01.met.vgwort.de\/na\/28ad46b21e314ef5acd6d7eb25cd2fa1\" alt=\"\" width=\"1\" height=\"1\" \/>As of Nov. 29, 2022, Google released Chrome in the 108 branch with fixes for 28 vulnerabilities (<a href=\"https:\/\/borncity.com\/win\/2022\/11\/30\/chrome-108-0-5359-71-72-61-released\/\">Chrome 108.0.5359.71\/72\/61 released<\/a>), and as of Dec. 2, 2022, there was the release of Chrome 108.0.5359.94\/.95 to fix a Type Confusion vulnerability in the V8 JavaScript engine. Here, Microsoft follows suit with the Chromium-based Edge browser.<\/p>\n<h2>Edge 108.0.1462.42 Stable Channel<\/h2>\n<p>According to the <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnotes-security#december-5-2022\" target=\"_blank\" rel=\"noopener\">release notes<\/a>, the update to Microsoft Edge Stable Channel (version 108.0.1462.42) includes a fix for the V8 Type Confusion vulnerability <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2022-4262\" target=\"_blank\" rel=\"noopener\">CVE-2022-4262<\/a>, which is already being exploited in the wild. In addition, Microsoft closes the following Edge-specific vulnerabilities with the update:<\/p>\n<ul>\n<li><a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2022-41115\" target=\"_blank\" rel=\"noopener\">CVE-2022-41115<\/a><\/li>\n<li><a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2022-44688\" target=\"_blank\" rel=\"noopener\">CVE-2022-44688<\/a><\/li>\n<li><a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2022-44708\" target=\"_blank\" rel=\"noopener\">CVE-2022-44708<\/a><\/li>\n<\/ul>\n<p>The list of all vulnerabilities can be found on <a href=\"https:\/\/msrc.microsoft.com\/update-guide\" target=\"_blank\" rel=\"noopener\">this web page<\/a>. The Edge should be updated automatically.<\/p>\n<blockquote><p>The colleagues from deskmodder.de reported <a href=\"https:\/\/www.deskmodder.de\/blog\/2022\/12\/05\/microsoft-edge-108-108-0-1462-41-schliesst-25-sicherheitsluecken\/\" target=\"_blank\" rel=\"noopener\">here<\/a> list a total of 25 closed vulnerabilities for the Edge 108.0.1462.41. But I didn't find any information about this version, only Edge 108.0.1462.42 is described. The <a href=\"https:\/\/learn.microsoft.com\/en-us\/deployedge\/microsoft-edge-relnote-stable-channel\" target=\"_blank\" rel=\"noopener\">release notes page<\/a> does refer to the Edge Stable, but in an inset they describe a fix for the <a href=\"https:\/\/msrc.microsoft.com\/update-guide\/vulnerability\/CVE-2022-4262\" target=\"_blank\" rel=\"noopener\">CVE-2022-4262<\/a> vulnerability in the Extended Stable channel.<\/p><\/blockquote>\n<h2>Feature Updates for Edge<\/h2>\n<p>The release notes also mention feature updates for Edge, ranging from new Graph APIs for managing cloud site lists for IE Mode , to more reliable web protection via the Microsoft Defender SmartScreen library. Furthermore, there are the following new policies:<\/p>\n<ul>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#encryptedclienthelloenabled\" target=\"_blank\" rel=\"noopener\">EncryptedClientHelloEnabled<\/a> &#8211; TLS Encrypted ClientHello Enabled<\/li>\n<li><a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#newtabpageapplauncherenabled\" target=\"_blank\" rel=\"noopener\">NewTabPageAppLauncherEnabled<\/a> &#8211; Hide App Launcher on Microsoft Edge new tab page<\/li>\n<\/ul>\n<p>And the policy <a href=\"https:\/\/learn.microsoft.com\/en-us\/DeployEdge\/microsoft-edge-policies#newsmartscreenlibraryenabled\" target=\"_blank\" rel=\"noopener\">NewSmartScreenLibraryEnabled<\/a> to activate the new SmartScreen library is now obsolete.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Microsoft has raised the Edge browser in the Stable Channel and Extended Stable Channel to version 108.0.1462.42 on December 5, 2022. It is a new development branch (108 version) that also fixes vulnerabilities reported by the Chromium team and already &hellip; <a href=\"https:\/\/borncity.com\/win\/2022\/12\/06\/edge-108-0-1462-42\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,580,1547,22],"tags":[320,195],"class_list":["post-27897","post","type-post","status-publish","format-standard","hentry","category-browser","category-security","category-software","category-update","tag-edge","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/27897","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=27897"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/27897\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=27897"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=27897"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=27897"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}