Microsoft advisory shows whether Edge keeps up with Chrome's patching

%3CLINGO-SUB%20id%3D%22lingo-sub-1157798%22%20slang%3D%22en-US%22%3EMicrosoft%20advisory%20shows%20whether%20Edge%20keeps%20up%20with%20Chrome's%20patching%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1157798%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22lia-align-left%22%3E%3CFONT%20size%3D%224%22%3EMicrosoft%20advisory%20shows%20whether%20Edge%20keeps%20up%20with%20Chrome's%20patching%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH3%20id%3D%22toc-hId-1086382709%22%20id%3D%22toc-hId-1086383477%22%20id%3D%22toc-hId-1086383477%22%20id%3D%22toc-hId-1086383477%22%20id%3D%22toc-hId-1086383477%22%3EThe%20advisory%20will%20be%20updated%20when%20Microsoft%20releases%20a%20new%20version%20of%20Edge%20that%20includes%20publicly%20disclosed%20security%20updates%20from%20the%20Chromium%20project.%3C%2FH3%3E%3CDIV%20class%3D%22constrain-970%22%3E%3CDIV%20class%3D%22lede-container%22%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22edge-browser-logo_microsoft-100816808-large%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F169584i7A3686F6F4D13F7F%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22edge-browser-logo_microsoft-100816808-large%22%20alt%3D%22edge-browser-logo_microsoft-100816808-large%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22cat%20%22%3E%3CP%3EMicrosoft%20has%20posted%20a%20security%20advisory%20that%20will%20record%20all%20updates%20to%20its%20new%20Chromium-based%20Edge%20browser%2C%20giving%20customers%20a%20way%20to%20monitor%20whether%20the%20company%20keeps%20up%20with%20Google's%20patching%20of%20Chrome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22This%20advisory%20will%20be%20updated%20whenever%20Microsoft%20releases%20a%20version%20of%20Microsoft%20Edge%20which%20incorporates%20publicly%20disclosed%20security%20updates%20from%20the%20Chromium%20project%2C%22%20the%20Redmond%2C%20Wash.%20firm%20wrote%20on%20the%20%3CA%20href%3D%22https%3A%2F%2Fportal.msrc.microsoft.com%2Fen-us%2Fsecurity-guidance%2Fadvisory%2FADV200002%22%20target%3D%22_blank%22%20rel%3D%22external%20noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Esupport%20document%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20of%20mid-day%20Wednesday%2C%20only%20one%20listing%20populated%20the%20advisory.%20The%20item%2C%20dated%20Jan.%2017%2C%20called%20out%20four%20CVE-identified%20vulnerabilities.%20(CVE%2C%20for%20%22Common%20Vulnerabilities%20and%20Exposures%2C%22%20is%20the%20most-used%20bug-naming%20standard.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20advisory%20also%20noted%20the%20Edge%20version%20number%20that%20included%20the%20patches%20and%20the%20corresponding%20version%20of%20Chromium%20that%20also%20quashed%20the%20bugs.%20Because%20Chrome%20assumes%20Chromium's%20version%20numbers%20without%20change%20-%20for%20some%20reason%2C%20Edge%20does%20not%20-%20the%20advisory%20was%20the%20first%20way%20%3CI%3Ethat%20was%20found%3C%2FI%3E%20to%20link%20a%20specific%20version%20of%20Edge%20to%20one%20of%20Chrome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20image-alt%3D%22screen-shot-2020-02-05-at-11.01.24-am-100829176-orig%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F169583iCA9CC9E351DADDAD%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22screen-shot-2020-02-05-at-11.01.24-am-100829176-orig%22%20alt%3D%22screen-shot-2020-02-05-at-11.01.24-am-100829176-orig%22%20%2F%3E%3C%2FSPAN%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%26nbsp%3B%3CDIV%20class%3D%22zoom-icon%22%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3EThis%20security%20advisory%20is%20supposed%20to%20list%20all%20Edge%20security%20updates.%20Comparing%20the%20version%20number%20of%20Edge%20to%20that%20of%20Chrome%20lets%20customers%20monitor%20whether%20Microsoft%20has%20kept%20up%20with%20Chromium's%2FChrome's%20fixes.%3C%2FP%3E%3CP%3EGoogle%20released%20Chrome%2079.0.3945.130%20-%20the%20Chromium%20version%20listed%20in%20the%20advisory%20-%20on%20Jan.%2016%2C%20saying%20%3CA%20href%3D%22https%3A%2F%2Fchromereleases.googleblog.com%2F2020%2F01%2Fstable-channel-update-for-desktop%2F_16.html%22%20target%3D%22_blank%22%20rel%3D%22external%20nofollow%20noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%20that%20the%20interim%20update%20included%20patches%20for%2011%20vulnerabilities%3C%2FA%3E.%20As%20usual%2C%20Google%20only%20identified%20four%20of%20the%2011%20by%20CVE.%20The%20quartet%20matched%20the%20four%20CVEs%20that%20Microsoft%20said%20were%20addressed%20in%20Edge.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMeanwhile%2C%20the%20Edge%20update%2C%20which%20Microsoft%20released%20Jan.%2017%20-%20one%20day%20after%20Chrome's%20-%20was%20marked%20as%20version%2079.0.309.68.%3C%2FP%3E%26nbsp%3B%3CP%3E(That's%20not%20the%20most%20current%20Edge%3B%20Microsoft%20updated%20the%20browser%20again%20on%20Jan.%2023%20to%2079.0.309.71.%20However%2C%20there%20was%20no%20sign%20that%20that%20version%20patched%20any%20vulnerabilities.%20For%20a%20complete%20listing%20of%20Edge%20updates%2C%20users%20can%20steer%20to%20the%20%3CA%20href%3D%22https%3A%2F%2Fwww.catalog.update.microsoft.com%2FSearch.aspx%3Fq%3Dmicrosoft%2520edge%2520stable%22%20target%3D%22_blank%22%20rel%3D%22external%20noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20Update%20Catalog%3C%2FA%3E%3B%20pre-filtered%20the%20results%20to%20show%20only%20those%20for%20the%20Stable%20build%20of%20the%20browser.)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdge%2079.0.309.68%20thus%20equals%20Chrome%2079.0.3945.130.%3C%2FP%3E%26nbsp%3B%3CP%3E%3CSTRONG%3EMicrosoft%20patched%20Edge%20just%20a%20day%20after%20Google%20refreshed%20Chrome%2C%20indicating%20that%20the%20former%20browser%20will%20not%20substantially%20lag%20behind%20the%20latter.%20If%20it%20had%2C%20attackers%20might%20have%20been%20able%20to%20use%20the%20interval%20to%20reverse%20engineer%20a%20patch%2C%20uncover%20the%20vulnerability%20and%20craft%20an%20exploit.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20unknown%20is%20the%20size%20of%20the%20gap%20between%20Google%20promoting%20a%20new%20version%20of%20Chrome%20to%20the%20Stable%20branch%20and%20Microsoft%20following%20suit%20with%20Edge.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20Tuesday%2C%20%3CA%20href%3D%22https%3A%2F%2Fchromereleases.googleblog.com%2F2020%2F02%2Fstable-channel-update-for-desktop.html%22%20target%3D%22_blank%22%20rel%3D%22external%20nofollow%20noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EGoogle%20released%20Chrome%2080%3C%2FA%3E%20-%20specifically%2C%20version%2080.0.3987.87%20-%20with%20new%20features%20as%20well%20as%2056%20security%20fixes.%20Google%20listed%2037%20of%20the%2056%20with%20CVE%20identifiers.%20Ten%20of%20the%2037%20were%20marked%20%22High%2C%22%20the%20second-most-serious%20ranking%20in%20Chrome's%20four-step%20rating%20system.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20of%202%20p.m.%20ET%20Wednesday%2C%20Microsoft%20had%20not%20updated%20Edge%20to%20reflect%20the%20Chrome's%20shift%20to%20version%2080.%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESource%3A%20%3CA%20href%3D%22https%3A%2F%2Fwww.computerworld.com%2Farticle%2F3519614%2Fmicrosoft-advisory-shows-whether-edge-keeps-up-with-chromes-patching.html%22%20target%3D%22_blank%22%20rel%3D%22external%20nofollow%20noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMicrosoft%20advisory%20shows%20whether%20Edge%20keeps%20up%20with%20Chrome's%20patching%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1157798%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3E80%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EChannel%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EChrome%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EEdge%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Emicrosoft%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Epatches%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStable%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EUpdate%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1158941%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20advisory%20shows%20whether%20Edge%20keeps%20up%20with%20Chrome's%20patching%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158941%22%20slang%3D%22en-US%22%3EGood%20Post%20and%20very%20interesting%20reading......%3CBR%20%2F%3E%3CBR%20%2F%3EDennis5mile%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1158952%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20advisory%20shows%20whether%20Edge%20keeps%20up%20with%20Chrome's%20patching%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1158952%22%20slang%3D%22en-US%22%3EThanks%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1160790%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20advisory%20shows%20whether%20Edge%20keeps%20up%20with%20Chrome's%20patching%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1160790%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EEdge%20version%2080%20stable%20released%26nbsp%3BVersion%2080.0.361.48%20(Official%20build)%20(64-bit)%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20such%20an%20awesome%20news.%20the%20gap%20between%20Chrome%20and%20Edge's%20release%20is%20very%20minimal%2C%20hopefully%20it%20will%20be%20less%20in%20the%20future.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Honored Contributor

Microsoft advisory shows whether Edge keeps up with Chrome's patching

 

The advisory will be updated when Microsoft releases a new version of Edge that includes publicly disclosed security updates from the Chromium project.

 

edge-browser-logo_microsoft-100816808-large

 

 

Microsoft has posted a security advisory that will record all updates to its new Chromium-based Edge browser, giving customers a way to monitor whether the company keeps up with Google's patching of Chrome.

 

"This advisory will be updated whenever Microsoft releases a version of Microsoft Edge which incorporates publicly disclosed security updates from the Chromium project," the Redmond, Wash. firm wrote on the support document.

 

As of mid-day Wednesday, only one listing populated the advisory. The item, dated Jan. 17, called out four CVE-identified vulnerabilities. (CVE, for "Common Vulnerabilities and Exposures," is the most-used bug-naming standard.)

 

The advisory also noted the Edge version number that included the patches and the corresponding version of Chromium that also quashed the bugs. Because Chrome assumes Chromium's version numbers without change - for some reason, Edge does not - the advisory was the first way that was found to link a specific version of Edge to one of Chrome.

 

screen-shot-2020-02-05-at-11.01.24-am-100829176-orig

 

 
 

This security advisory is supposed to list all Edge security updates. Comparing the version number of Edge to that of Chrome lets customers monitor whether Microsoft has kept up with Chromium's/Chrome's fixes.

Google released Chrome 79.0.3945.130 - the Chromium version listed in the advisory - on Jan. 16, saying here that the interim update included patches for 11 vulnerabilities. As usual, Google only identified four of the 11 by CVE. The quartet matched the four CVEs that Microsoft said were addressed in Edge.

 

Meanwhile, the Edge update, which Microsoft released Jan. 17 - one day after Chrome's - was marked as version 79.0.309.68.

 

(That's not the most current Edge; Microsoft updated the browser again on Jan. 23 to 79.0.309.71. However, there was no sign that that version patched any vulnerabilities. For a complete listing of Edge updates, users can steer to the Microsoft Update Catalog; pre-filtered the results to show only those for the Stable build of the browser.)

 

Edge 79.0.309.68 thus equals Chrome 79.0.3945.130.

 

Microsoft patched Edge just a day after Google refreshed Chrome, indicating that the former browser will not substantially lag behind the latter. If it had, attackers might have been able to use the interval to reverse engineer a patch, uncover the vulnerability and craft an exploit.

 

Still unknown is the size of the gap between Google promoting a new version of Chrome to the Stable branch and Microsoft following suit with Edge.

 

On Tuesday, Google released Chrome 80 - specifically, version 80.0.3987.87 - with new features as well as 56 security fixes. Google listed 37 of the 56 with CVE identifiers. Ten of the 37 were marked "High," the second-most-serious ranking in Chrome's four-step rating system.

 

As of 2 p.m. ET Wednesday, Microsoft had not updated Edge to reflect the Chrome's shift to version 80. 

 

 

Source: Microsoft advisory shows whether Edge keeps up with Chrome's patching

3 Replies
Highlighted
Good Post and very interesting reading......

Dennis5mile
Highlighted
Highlighted

Edge version 80 stable released Version 80.0.361.48 (Official build) (64-bit)

 

This is such an awesome news. the gap between Chrome and Edge's release is very minimal, hopefully it will be less in the future.