Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Chrome & Chromium
Google Chrome 76.0.3809.87 stable update
Message
<blockquote data-quote="Gandalf_The_Grey" data-source="post: 827094" data-attributes="member: 52096"><p><span style="font-size: 22px"><strong><a href="https://chromereleases.googleblog.com/2019/07/stable-channel-update-for-desktop_30.html" target="_blank">Stable Channel Update for Desktop</a></strong></span></p><p>Tuesday, July 30, 2019</p><p>The Chrome team is delighted to announce the promotion of <strong>Chrome 76</strong> to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.</p><p></p><p>Chrome <strong>76.0.3809.87</strong> contains a number of fixes and improvements -- a list of changes is available in the<a href="https://chromium.googlesource.com/chromium/src/+log/75.0.3770.142..76.0.3809.87?pretty=fuller&n=10000" target="_blank"> log</a>. Watch out for upcoming<a href="https://chrome.blogspot.com/" target="_blank"> Chrome</a> and<a href="https://blog.chromium.org/" target="_blank"> Chromium</a> blog posts about new features and big efforts delivered in 76.</p><p></p><p></p><p><span style="font-size: 22px"><strong>Security Fixes and Rewards</strong></span></p><p><span style="font-size: 22px"><strong></strong></span></p><p><span style="font-size: 22px"><strong>Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.</strong></span></p><p>This update includes <a href="https://bugs.chromium.org/p/chromium/issues/list?can=1&q=type%3Abug-security+os%3DAndroid%2Cios%2Clinux%2Cmac%2Cwindows%2Call+label%3ARelease-0-M76" target="_blank">43</a> security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the <a href="https://sites.google.com/a/chromium.org/dev/Home/chromium-security" target="_blank">Chrome Security Page</a> for more information.</p><p></p><p>[$10000][<a href="https://crbug.com/977462" target="_blank">977462</a>] High CVE-2019-5850: Use-after-free in offline page fetcher. Reported by Brendon Tiszka on 2019-06-21</p><p>[$6000][<a href="https://crbug.com/956947" target="_blank">956947</a>] High CVE-2019-5860: Use-after-free in PDFium. Reported by Anonymous on 2019-04-26</p><p>[$3000][<a href="https://crbug.com/976627" target="_blank">976627</a>] High CVE-2019-5853: Memory corruption in regexp length check. Reported by yngwei(@yngweijw) of IIE Varas and sakura(@eternalsakura13) of Tecent Xuanwu Lab on 2019-06-19</p><p>[$3000][<a href="https://crbug.com/977107" target="_blank">977107</a>] High CVE-2019-5851: Use-after-poison in offline audio context. Reported by Zhe Jin（金哲），Luyao Liu(刘路遥) from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd on 2019-06-20</p><p>[$TBD][<a href="https://crbug.com/959438" target="_blank">959438</a>] High CVE-2019-5859: res: URIs can load alternative browsers. Reported by James Lee (@Windowsrcer) of Kryptos Logic on 2019-05-03</p><p>[$5000][<a href="https://crbug.com/964245" target="_blank">964245</a>] Medium CVE-2019-5856: Insufficient checks on filesystem: URI permissions. Reported by Yongke Wang of Tencent's Xuanwu Lab (xlab.tencent.com) on 2019-05-17</p><p>[$N/A][<a href="https://crbug.com/943494" target="_blank">943494</a>] Medium CVE-2019-5863: Use-after-free in WebUSB on Windows. Reported by Yuxiang Li (@Xbalien29) of Tencent Security Platform Department on 2019-03-19</p><p>[$N/A][<a href="https://crbug.com/964872" target="_blank">964872</a>] Medium CVE-2019-5855: Integer overflow in PDFium. Reported by Zhen Zhou of NSFOCUS Security Team on 2019-05-20</p><p>[$TBD][<a href="https://crbug.com/973103" target="_blank">973103</a>] Medium CVE-2019-5865: Site isolation bypass from compromised renderer. Reported by Ivan Fratric of Google Project Zero on 2019-06-11</p><p>[$500][<a href="https://crbug.com/960209" target="_blank">960209</a>] Low CVE-2019-5858: Insufficient filtering of Open URL service parameters. Reported by evi1m0 of Bilibili Security Team on 2019-05-07</p><p>[$500][<a href="https://crbug.com/936900" target="_blank">936900</a>] Low CVE-2019-5864: Insufficient port filtering in CORS for extensions. Reported by Devin Grindle on 2019-02-28</p><p>[$TBD][<a href="https://crbug.com/946260" target="_blank">946260</a>] Low CVE-2019-5862: AppCache not robust to compromised renderers. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-03-26</p><p>[$TBD][<a href="https://crbug.com/951525" target="_blank">951525</a>] Low CVE-2019-5861: Click location incorrectly checked. Reported by Robin Linus ( robinlinus.com ) on 2019-04-10</p><p>[$N/A][<a href="https://crbug.com/961237" target="_blank">961237</a>] Low CVE-2019-5857: Comparison of -0 and null yields crash. Reported by cloudfuzzer on 2019-05-09</p><p>[$N/A][<a href="https://crbug.com/966263" target="_blank">966263</a>] Low CVE-2019-5854: Integer overflow in PDFium text rendering. Reported by Zhen Zhou of NSFOCUS Security Team on 2019-05-23</p><p>[$TBD][<a href="https://crbug.com/976713" target="_blank">976713</a>] Low CVE-2019-5852: Object leak of utility functions. Reported by David Erceg on 2019-06-19</p><p>We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.</p><p></p><p>As usual, our ongoing internal security work was responsible for a wide range of fixes:</p><p></p><ul> <li data-xf-list-type="ul">[<a href="https://crbug.com/988889" target="_blank">988889</a>] Various fixes from internal audits, fuzzing and other initiatives</li> </ul><p></p><p>Many of our security bugs are detected using <a href="https://code.google.com/p/address-sanitizer/wiki/AddressSanitizer" target="_blank">AddressSanitizer</a>, <a href="https://code.google.com/p/memory-sanitizer/wiki/MemorySanitizer" target="_blank">MemorySanitizer</a>, <a href="https://www.chromium.org/developers/testing/undefinedbehaviorsanitizer" target="_blank">UndefinedBehaviorSanitizer</a>, <a href="https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-integrity" target="_blank">Control Flow Integrity</a>, <a href="https://sites.google.com/a/chromium.org/dev/developers/testing/libfuzzer" target="_blank">libFuzzer</a>, or <a href="http://lcamtuf.coredump.cx/afl/" target="_blank">AFL</a>.</p><p></p><p>Interested in switching release channels? Find out how <a href="https://www.chromium.org/getting-involved/dev-channel" target="_blank">here</a>. If you find a new issue, please let us know by <a href="https://crbug.com/" target="_blank">filing a bug</a>. The <a href="https://productforums.google.com/forum/#!forum/chrome" target="_blank">community help forum</a> is also a great place to reach out for help or learn about common issues.</p><p></p><p>Thank you,</p><p>Abdul Syed</p></blockquote><p></p>
[QUOTE="Gandalf_The_Grey, post: 827094, member: 52096"] [SIZE=6][B][URL='https://chromereleases.googleblog.com/2019/07/stable-channel-update-for-desktop_30.html']Stable Channel Update for Desktop[/URL][/B][/SIZE] Tuesday, July 30, 2019 The Chrome team is delighted to announce the promotion of [B]Chrome 76[/B] to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks. Chrome [B]76.0.3809.87[/B] contains a number of fixes and improvements -- a list of changes is available in the[URL='https://chromium.googlesource.com/chromium/src/+log/75.0.3770.142..76.0.3809.87?pretty=fuller&n=10000'] log[/URL]. Watch out for upcoming[URL='https://chrome.blogspot.com/'] Chrome[/URL] and[URL='https://blog.chromium.org/'] Chromium[/URL] blog posts about new features and big efforts delivered in 76. [SIZE=6][B]Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.[/B][/SIZE] This update includes [URL='https://bugs.chromium.org/p/chromium/issues/list?can=1&q=type%3Abug-security+os%3DAndroid%2Cios%2Clinux%2Cmac%2Cwindows%2Call+label%3ARelease-0-M76']43[/URL] security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the [URL='https://sites.google.com/a/chromium.org/dev/Home/chromium-security']Chrome Security Page[/URL] for more information. [$10000][[URL='https://crbug.com/977462']977462[/URL]] High CVE-2019-5850: Use-after-free in offline page fetcher. Reported by Brendon Tiszka on 2019-06-21 [$6000][[URL='https://crbug.com/956947']956947[/URL]] High CVE-2019-5860: Use-after-free in PDFium. Reported by Anonymous on 2019-04-26 [$3000][[URL='https://crbug.com/976627']976627[/URL]] High CVE-2019-5853: Memory corruption in regexp length check. Reported by yngwei(@yngweijw) of IIE Varas and sakura(@eternalsakura13) of Tecent Xuanwu Lab on 2019-06-19 [$3000][[URL='https://crbug.com/977107']977107[/URL]] High CVE-2019-5851: Use-after-poison in offline audio context. Reported by Zhe Jin（金哲），Luyao Liu(刘路遥) from Chengdu Security Response Center of Qihoo 360 Technology Co. Ltd on 2019-06-20 [$TBD][[URL='https://crbug.com/959438']959438[/URL]] High CVE-2019-5859: res: URIs can load alternative browsers. Reported by James Lee (@Windowsrcer) of Kryptos Logic on 2019-05-03 [$5000][[URL='https://crbug.com/964245']964245[/URL]] Medium CVE-2019-5856: Insufficient checks on filesystem: URI permissions. Reported by Yongke Wang of Tencent's Xuanwu Lab (xlab.tencent.com) on 2019-05-17 [$N/A][[URL='https://crbug.com/943494']943494[/URL]] Medium CVE-2019-5863: Use-after-free in WebUSB on Windows. Reported by Yuxiang Li (@Xbalien29) of Tencent Security Platform Department on 2019-03-19 [$N/A][[URL='https://crbug.com/964872']964872[/URL]] Medium CVE-2019-5855: Integer overflow in PDFium. Reported by Zhen Zhou of NSFOCUS Security Team on 2019-05-20 [$TBD][[URL='https://crbug.com/973103']973103[/URL]] Medium CVE-2019-5865: Site isolation bypass from compromised renderer. Reported by Ivan Fratric of Google Project Zero on 2019-06-11 [$500][[URL='https://crbug.com/960209']960209[/URL]] Low CVE-2019-5858: Insufficient filtering of Open URL service parameters. Reported by evi1m0 of Bilibili Security Team on 2019-05-07 [$500][[URL='https://crbug.com/936900']936900[/URL]] Low CVE-2019-5864: Insufficient port filtering in CORS for extensions. Reported by Devin Grindle on 2019-02-28 [$TBD][[URL='https://crbug.com/946260']946260[/URL]] Low CVE-2019-5862: AppCache not robust to compromised renderers. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-03-26 [$TBD][[URL='https://crbug.com/951525']951525[/URL]] Low CVE-2019-5861: Click location incorrectly checked. Reported by Robin Linus ( robinlinus.com ) on 2019-04-10 [$N/A][[URL='https://crbug.com/961237']961237[/URL]] Low CVE-2019-5857: Comparison of -0 and null yields crash. Reported by cloudfuzzer on 2019-05-09 [$N/A][[URL='https://crbug.com/966263']966263[/URL]] Low CVE-2019-5854: Integer overflow in PDFium text rendering. Reported by Zhen Zhou of NSFOCUS Security Team on 2019-05-23 [$TBD][[URL='https://crbug.com/976713']976713[/URL]] Low CVE-2019-5852: Object leak of utility functions. Reported by David Erceg on 2019-06-19 We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel. As usual, our ongoing internal security work was responsible for a wide range of fixes: [LIST] [*][[URL='https://crbug.com/988889']988889[/URL]] Various fixes from internal audits, fuzzing and other initiatives [/LIST] Many of our security bugs are detected using [URL='https://code.google.com/p/address-sanitizer/wiki/AddressSanitizer']AddressSanitizer[/URL], [URL='https://code.google.com/p/memory-sanitizer/wiki/MemorySanitizer']MemorySanitizer[/URL], [URL='https://www.chromium.org/developers/testing/undefinedbehaviorsanitizer']UndefinedBehaviorSanitizer[/URL], [URL='https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-integrity']Control Flow Integrity[/URL], [URL='https://sites.google.com/a/chromium.org/dev/developers/testing/libfuzzer']libFuzzer[/URL], or [URL='http://lcamtuf.coredump.cx/afl/']AFL[/URL]. Interested in switching release channels? Find out how [URL='https://www.chromium.org/getting-involved/dev-channel']here[/URL]. If you find a new issue, please let us know by [URL='https://crbug.com/']filing a bug[/URL]. The [URL='https://productforums.google.com/forum/#!forum/chrome']community help forum[/URL] is also a great place to reach out for help or learn about common issues. Thank you, Abdul Syed [/QUOTE]
Insert quotes…
Verification
Post reply
Top
