{"id":265706,"date":"2022-05-25T15:34:44","date_gmt":"2022-05-25T13:34:44","guid":{"rendered":"https:\/\/www.borncity.com\/blog\/?p=265706"},"modified":"2022-05-25T15:40:51","modified_gmt":"2022-05-25T13:40:51","slug":"chrome-102-0-5005-61-62-63-fixen-schwachstellen","status":"publish","type":"post","link":"https:\/\/borncity.com\/blog\/2022\/05\/25\/chrome-102-0-5005-61-62-63-fixen-schwachstellen\/","title":{"rendered":"Chrome 102.0.5005.61\/62\/63 fixen kritische Schwachstellen"},"content":{"rendered":"<p><img decoding=\"async\" style=\"float: left; margin: 0px 10px 0px 0px; display: inline;\" src=\"https:\/\/borncity.com\/blog\/wp-content\/uploads\/2021\/06\/Chrome-01.jpg\" align=\"left\" \/>[<a href=\"https:\/\/borncity.com\/win\/2022\/05\/25\/chrome-102-0-5005-61-62-63-fixen-schwachstellen\/\" target=\"_blank\" rel=\"noopener\">English<\/a>]Google hat zum 24. Mai 2022 die Updates des 102.0.5005.61\/62\/63 Google Chrome Browsers f\u00fcr Windows und Mac auf dem Desktop im Stable Channel freigegeben (Chrome 102 wird auch im Stable Channel f\u00fcr Windows und Mac aufgenommen). Weiterhin wurde unter Android das Update auf die Version 102.0.5005.58\/59 <a href=\"https:\/\/chromereleases.googleblog.com\/2022\/05\/chrome-for-android-update_01678544884.html\" target=\"_blank\" rel=\"noopener\">freigegeben<\/a>.<\/p>\n<p><!--more--><\/p>\n<h2>Google Chrome 102.0.5005.61\/62\/63<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/vg02.met.vgwort.de\/na\/d5e0a95ef20a4092bdd5e2c482652f58\" alt=\"\" width=\"1\" height=\"1\" \/>Der <a href=\"https:\/\/chromereleases.googleblog.com\/2022\/05\/stable-channel-update-for-desktop_24.html\" target=\"_blank\" rel=\"noopener\">betreffende Eintrag<\/a> f\u00fcr den Chrome 102.0.5005.61\/62\/63 findet sich im <a href=\"https:\/\/chromereleases.googleblog.com\/\" target=\"_blank\" rel=\"noopener\">Google-Blog<\/a>. Mit diesem Update werden 32 Schwachstellen (eine davon ist kritisch) geschlossen, wobei Google nur folgende Schwachstellen explizit auff\u00fchrt.<\/p>\n<ul>\n<li>[$TBD][1324864] Critical CVE-2022-1853: Use after free in Indexed DB. Reported by Anonymous on 2022-05-12<\/li>\n<li>[$10000][1320024] High CVE-2022-1854: Use after free in ANGLE. Reported by SeongHwan Park (SeHwa) on 2022-04-27<\/li>\n<li>[$7500][1228661] High CVE-2022-1855: Use after free in Messaging. Reported by Anonymous on 2021-07-13<\/li>\n<li>[$3000][1323239] High CVE-2022-1856: Use after free in User Education. Reported by Nan Wang(@eternalsakura13) and Guang Gong of 360 Alpha Lab\u00a0 on 2022-05-06<\/li>\n<li>[$2000][1227995] High CVE-2022-1857: Insufficient policy enforcement in File System API. Reported by Daniel Rhea on 2021-07-11<\/li>\n<li>[$1000][1314310] High CVE-2022-1858: Out of bounds read in DevTools. Reported by EllisVlad on 2022-04-07<\/li>\n<li>[$1000][1322744] High CVE-2022-1859: Use after free in Performance Manager. Reported by Guannan Wang (@Keenan7310) of Tencent Security Xuanwu Lab on 2022-05-05<\/li>\n<li>[$TBD][1297209] High CVE-2022-1860: Use after free in UI Foundations. Reported by @ginggilBesel on 2022-02-15<\/li>\n<li>[$TBD][1316846] High CVE-2022-1861: Use after free in Sharing. Reported by Khalil Zhani on 2022-04-16<\/li>\n<li>[$5000][1236325] Medium CVE-2022-1862: Inappropriate implementation in Extensions. Reported by Alesandro Ortiz on 2021-08-04<\/li>\n<li>[$5000][1292870] Medium CVE-2022-1863: Use after free in Tab Groups. Reported by David Erceg on 2022-02-01<\/li>\n<li>[$5000][1320624] Medium CVE-2022-1864: Use after free in WebApp Installs. Reported by Yuntao You (@GraVity0) of Bytedance Wuheng Lab on 2022-04-28<\/li>\n<li>[$3000][1289192] Medium CVE-2022-1865: Use after free in Bookmarks. Reported by Rong Jian of VRI on 2022-01-20<\/li>\n<li>[$3000][1292264] Medium CVE-2022-1866: Use after free in Tablet Mode. Reported by @ginggilBesel on 2022-01-29<\/li>\n<li>[$3000][1315563] Medium CVE-2022-1867: Insufficient validation of untrusted input in Data Transfer. Reported by Micha\u0142 Bentkowski of Securitum on 2022-04-12<\/li>\n<li>[$TBD][1301203] Medium CVE-2022-1868: Inappropriate implementation in Extensions API. Reported by Alesandro Ortiz on 2022-02-28<\/li>\n<li>[$NA][1309467] Medium CVE-2022-1869: Type Confusion in V8. Reported by Man Yue Mo of GitHub Security Lab on 2022-03-23<\/li>\n<li>[$TBD][1323236] Medium CVE-2022-1870: Use after free in App Service. Reported by Nan Wang(@eternalsakura13) and Guang Gong of 360 Alpha Lab\u00a0 on 2022-05-06<\/li>\n<li>[$7000][1308199] Low CVE-2022-1871: Insufficient policy enforcement in File System API. Reported by Thomas Orlita\u00a0 on 2022-03-21<\/li>\n<li>[$7000][1310461] Low CVE-2022-1872: Insufficient policy enforcement in Extensions API. Reported by ChaobinZhang on 2022-03-26<\/li>\n<li>[$2000][1305394] Low CVE-2022-1873: Insufficient policy enforcement in COOP. Reported by NDevTK on 2022-03-11<\/li>\n<li>[$500][1251588] Low CVE-2022-1874: Insufficient policy enforcement in Safe Browsing. Reported by hjy79425575 on 2021-09-21<\/li>\n<li>[$500][1306443] Low CVE-2022-1875: Inappropriate implementation in PDF. Reported by NDevTK on 2022-03-15<\/li>\n<li>[$TBD][1313600] Low CVE-2022-1876: Heap buffer overflow in DevTools. Reported by @ginggilBesel on 2022-04-06<\/li>\n<\/ul>\n<p>Die Chrome-Version f\u00fcr Windows, Mac und Linux wird in den n\u00e4chsten Tagen \u00fcber die automatische Update-Funktion auf die Systeme ausgerollt. Man kann den Browser auch manuell (\u00fcber das Men\u00fc und den Befehl <em>\u00dcber Google Chrome<\/em>) aktualisieren. Die aktuelle Build des Chrome-Browsers l\u00e4sst sich auch <a href=\"https:\/\/www.google.com\/chrome\/\" target=\"_blank\" rel=\"noopener\">hier herunterladen<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[English]Google hat zum 24. Mai 2022 die Updates des 102.0.5005.61\/62\/63 Google Chrome Browsers f\u00fcr Windows und Mac auf dem Desktop im Stable Channel freigegeben (Chrome 102 wird auch im Stable Channel f\u00fcr Windows und Mac aufgenommen). Weiterhin wurde unter Android &hellip; <a href=\"https:\/\/borncity.com\/blog\/2022\/05\/25\/chrome-102-0-5005-61-62-63-fixen-schwachstellen\/\">Weiterlesen <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1356,426,185],"tags":[406,4328,4315],"class_list":["post-265706","post","type-post","status-publish","format-standard","hentry","category-google-chrome-internet","category-sicherheit","category-update","tag-chrome","tag-sicherheit","tag-update"],"_links":{"self":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/265706","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=265706"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/posts\/265706\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/media?parent=265706"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/categories?post=265706"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/blog\/wp-json\/wp\/v2\/tags?post=265706"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}