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
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 74.0.3729.108 Stable Channel Update
Message
<blockquote data-quote="Gandalf_The_Grey" data-source="post: 811448" data-attributes="member: 52096"><p><span style="font-size: 22px"><strong><a href="https://chromereleases.googleblog.com/2019/04/stable-channel-update-for-desktop_23.html" target="_blank">Stable Channel Update for Desktop</a></strong></span></p><p>Tuesday, April 23, 2019</p><p>The Chrome team is delighted to announce the promotion of Chrome 74 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.</p><p></p><p>Chrome 74.0.3729.108 contains a number of fixes and improvements -- a list of changes is available in the<a href="https://chromium.googlesource.com/chromium/src/+log/73.0.3683.103..74.0.3729.108?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 74.</p><p></p><p></p><p><strong>Security Fixes and Rewards</strong></p><p>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.</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-M74" target="_blank">39</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>[$3000][<a href="https://crbug.com/913320" target="_blank">913320</a>] High CVE-2019-5805: Use after free in PDFium. Reported by Anonymous on 2018-12-10</p><p>[$3000][<a href="https://crbug.com/943087" target="_blank">943087</a>] High CVE-2019-5806: Integer overflow in Angle. Reported by Wen Xu of SSLab, Georgia Tech on 2019-03-18</p><p>[$3000][<a href="https://crbug.com/945644" target="_blank">945644</a>] High CVE-2019-5807: Memory corruption in V8. Reported by TimGMichaud of Leviathan Security Group. on 2019-03-26</p><p>[$3000][<a href="https://crbug.com/947029" target="_blank">947029</a>] High CVE-2019-5808: Use after free in Blink. Reported by cloudfuzzer on 2019-03-28</p><p>[$N/A][<a href="https://crbug.com/941008" target="_blank">941008</a>] High CVE-2019-5809: Use after free in Blink. Reported by Mark Brand of Google Project Zero on 2019-03-12</p><p>[$2000+$1,337][<a href="https://crbug.com/916838" target="_blank">916838</a>] Medium CVE-2019-5810: User information disclosure in Autofill. Reported by Mark Amery on 2018-12-20</p><p>[$2000][<a href="https://crbug.com/771815" target="_blank">771815</a>] Medium CVE-2019-5811: CORS bypass in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-10-04</p><p>[$2000][<a href="https://crbug.com/925598" target="_blank">925598</a>] Medium CVE-2019-5812: URL spoof in Omnibox on iOS. Reported by Khalil Zhani on 2019-01-26</p><p>[$2000][<a href="https://crbug.com/942699" target="_blank">942699</a>] Medium CVE-2019-5813: Out of bounds read in V8. Reported by Aleksandar Nikolic of Cisco Talos on 2019-03-15</p><p>[$1000][<a href="https://crbug.com/930057" target="_blank">930057</a>] Medium CVE-2019-5814: CORS bypass in Blink. Reported by @AaylaSecura1138 on 2019-02-08</p><p>[$1000][<a href="https://crbug.com/930663" target="_blank">930663</a>] Medium CVE-2019-5815: Heap buffer overflow in Blink. Reported by Nicolas Grégoire, Agarri on 2019-02-11</p><p>[$1000][<a href="https://crbug.com/940245" target="_blank">940245</a>] Medium CVE-2019-5816: Exploit persistence extension on Android. Reported by Yongke Wang of Tencent's Xuanwu Lab (xlab.tencent.com) on 2019-03-10</p><p>[$1000][<a href="https://crbug.com/943709" target="_blank">943709</a>] Medium CVE-2019-5817: Heap buffer overflow in Angle on Windows. Reported by Wen Xu of SSLab, Georgia Tech on 2019-03-19</p><p>[$500][<a href="https://crbug.com/929962" target="_blank">929962</a>] Medium CVE-2019-5818: Uninitialized value in media reader. Reported by Adrian Tolbaru on 2019-02-08</p><p>[$N/A][<a href="https://crbug.com/919356" target="_blank">919356</a>] Medium CVE-2019-5819: Incorrect escaping in developer tools. Reported by Svyat Mitin on 2019-01-06</p><p>[$N/A][<a href="https://crbug.com/919635" target="_blank">919635</a>] Medium CVE-2019-5820: Integer overflow in PDFium. Reported by pdknsk on 2019-01-07</p><p>[$N/A][<a href="https://crbug.com/919640" target="_blank">919640</a>] Medium CVE-2019-5821: Integer overflow in PDFium. Reported by pdknsk on 2019-01-07</p><p>[$500][<a href="https://crbug.com/926105" target="_blank">926105</a>] Low CVE-2019-5822: CORS bypass in download manager. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-01-29</p><p>[$500][<a href="https://crbug.com/930154" target="_blank">930154</a>] Low CVE-2019-5823: Forced navigation from service worker. Reported by David Erceg on 2019-02-08</p><p></p><p></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><p></p><p>[<a href="https://crbug.com/955186" target="_blank">955186</a>] Various fixes from internal audits, fuzzing and other initiatives</p><p></p><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: 811448, member: 52096"] [SIZE=6][B][URL='https://chromereleases.googleblog.com/2019/04/stable-channel-update-for-desktop_23.html']Stable Channel Update for Desktop[/URL][/B][/SIZE] Tuesday, April 23, 2019 The Chrome team is delighted to announce the promotion of Chrome 74 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks. Chrome 74.0.3729.108 contains a number of fixes and improvements -- a list of changes is available in the[URL='https://chromium.googlesource.com/chromium/src/+log/73.0.3683.103..74.0.3729.108?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 74. [B]Security Fixes and Rewards[/B] 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. 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-M74']39[/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. [$3000][[URL='https://crbug.com/913320']913320[/URL]] High CVE-2019-5805: Use after free in PDFium. Reported by Anonymous on 2018-12-10 [$3000][[URL='https://crbug.com/943087']943087[/URL]] High CVE-2019-5806: Integer overflow in Angle. Reported by Wen Xu of SSLab, Georgia Tech on 2019-03-18 [$3000][[URL='https://crbug.com/945644']945644[/URL]] High CVE-2019-5807: Memory corruption in V8. Reported by TimGMichaud of Leviathan Security Group. on 2019-03-26 [$3000][[URL='https://crbug.com/947029']947029[/URL]] High CVE-2019-5808: Use after free in Blink. Reported by cloudfuzzer on 2019-03-28 [$N/A][[URL='https://crbug.com/941008']941008[/URL]] High CVE-2019-5809: Use after free in Blink. Reported by Mark Brand of Google Project Zero on 2019-03-12 [$2000+$1,337][[URL='https://crbug.com/916838']916838[/URL]] Medium CVE-2019-5810: User information disclosure in Autofill. Reported by Mark Amery on 2018-12-20 [$2000][[URL='https://crbug.com/771815']771815[/URL]] Medium CVE-2019-5811: CORS bypass in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-10-04 [$2000][[URL='https://crbug.com/925598']925598[/URL]] Medium CVE-2019-5812: URL spoof in Omnibox on iOS. Reported by Khalil Zhani on 2019-01-26 [$2000][[URL='https://crbug.com/942699']942699[/URL]] Medium CVE-2019-5813: Out of bounds read in V8. Reported by Aleksandar Nikolic of Cisco Talos on 2019-03-15 [$1000][[URL='https://crbug.com/930057']930057[/URL]] Medium CVE-2019-5814: CORS bypass in Blink. Reported by @AaylaSecura1138 on 2019-02-08 [$1000][[URL='https://crbug.com/930663']930663[/URL]] Medium CVE-2019-5815: Heap buffer overflow in Blink. Reported by Nicolas Grégoire, Agarri on 2019-02-11 [$1000][[URL='https://crbug.com/940245']940245[/URL]] Medium CVE-2019-5816: Exploit persistence extension on Android. Reported by Yongke Wang of Tencent's Xuanwu Lab (xlab.tencent.com) on 2019-03-10 [$1000][[URL='https://crbug.com/943709']943709[/URL]] Medium CVE-2019-5817: Heap buffer overflow in Angle on Windows. Reported by Wen Xu of SSLab, Georgia Tech on 2019-03-19 [$500][[URL='https://crbug.com/929962']929962[/URL]] Medium CVE-2019-5818: Uninitialized value in media reader. Reported by Adrian Tolbaru on 2019-02-08 [$N/A][[URL='https://crbug.com/919356']919356[/URL]] Medium CVE-2019-5819: Incorrect escaping in developer tools. Reported by Svyat Mitin on 2019-01-06 [$N/A][[URL='https://crbug.com/919635']919635[/URL]] Medium CVE-2019-5820: Integer overflow in PDFium. Reported by pdknsk on 2019-01-07 [$N/A][[URL='https://crbug.com/919640']919640[/URL]] Medium CVE-2019-5821: Integer overflow in PDFium. Reported by pdknsk on 2019-01-07 [$500][[URL='https://crbug.com/926105']926105[/URL]] Low CVE-2019-5822: CORS bypass in download manager. Reported by Jun Kokatsu, Microsoft Browser Vulnerability Research on 2019-01-29 [$500][[URL='https://crbug.com/930154']930154[/URL]] Low CVE-2019-5823: Forced navigation from service worker. Reported by David Erceg on 2019-02-08 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: [[URL='https://crbug.com/955186']955186[/URL]] Various fixes from internal audits, fuzzing and other initiatives 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