Chrome Releases: January 2017

Dev Channel Update for Desktop

Tuesday, January 31, 2017

The dev channel has been updated to 57.0.2987.19 for Windows, Mac and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Krishna Govind Google Chrome

Dev Channel Update for Desktop

Friday, January 27, 2017

The dev channel has been updated to 57.0.2987.13 for Windows, Mac and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Krishna Govind Google Chrome

Beta Channel Update for Chrome OS

Thursday, January 26, 2017

hereforumfiling a bugFind out how Google Chrome

Stable Channel Update for Desktop

Wednesday, January 25, 2017

The Chrome team is delighted to announce the promotion of Chrome 56 to the stable channel - 56.0.2924.76 for Windows, Mac and Linux. This will roll out over the coming days/weeks.

Chrome 56.0.2924.76 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 56.

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.

This update includes 51 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

[$8837][671102] High CVE-2017-5007: Universal XSS in Blink. Credit to Mariusz Mlynski

[$8000][673170] High CVE-2017-5006: Universal XSS in Blink. Credit to Mariusz Mlynski

[$8000][668552] High CVE-2017-5008: Universal XSS in Blink. Credit to Mariusz Mlynski

[$7500][663476] High CVE-2017-5010: Universal XSS in Blink. Credit to Mariusz Mlynski

[$3000][662859] High CVE-2017-5011: Unauthorised file access in Devtools. Credit to Khalil Zhani

[$3000][667504] High CVE-2017-5009: Out of bounds memory access in WebRTC. Credit to Sean Stanek and Chip Bradford

[$5500][681843] High CVE-2017-5012: Heap overflow in V8. Credit to Gergely Nagy (Tresorit)
[$3000][653555] High CVE-2017-5028: Insufficient data validation in V8.

[$2000][677716] Medium CVE-2017-5013: Address spoofing in Omnibox. Credit to Haosheng Wang (@gnehsoah)

[$2000][675332] Medium CVE-2017-5014: Heap overflow in Skia. Credit to sweetchip

[$2000][673971] Medium CVE-2017-5015: Address spoofing in Omnibox. Credit to Armin Razmdjou

[$2000][666714] Medium CVE-2017-5019: Use after free in Renderer. Credit to Wadih Matar

[$1000][673163] Medium CVE-2017-5016: UI spoofing in Blink. Credit to Haosheng Wang (@gnehsoah)

[$500][676975] Medium CVE-2017-5017: Uninitialised memory access in webm video. Credit to Dan Berman

[$500][668665] Medium CVE-2017-5018: Universal XSS in chrome://apps. Credit to Rob Wu

[$TBD][668653] Medium CVE-2017-5020: Universal XSS in chrome://downloads. Credit to Rob Wu

[$N/A][663726] Low CVE-2017-5021: Use after free in Extensions. Credit to Rob Wu

[$N/A][663620] Low CVE-2017-5022: Bypass of Content Security Policy in Blink. Credit to evi1m0#ly.com

[$N/A][651443] Low CVE-2017-5023: Type confusion in metrics. Credit to the UK's National Cyber Security Centre (NCSC)

[$N/A][643951] Low CVE-2017-5024: Heap overflow in FFmpeg. Credit to Paul Mehta

[$N/A][643950] Low CVE-2017-5025: Heap overflow in FFmpeg. Credit to Paul Mehta

[$500][634108] Low CVE-2017-5026: UI spoofing. Credit to Ronni Skansing

[$N/A][661126] Low CVE-2017-5027: Bypass of Content Security Policy in Blink. Credit to 李普君 of 无声信息技术PKAV Team

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:

[685349] Various fixes from internal audits, fuzzing and other initiatives

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, Control Flow Integrity, or libFuzzer.

Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Richard Bustamante

Google Chrome

Beta Channel Update for Desktop

Wednesday, January 25, 2017

The beta channel has been updated to 56.0.2924.76 for Windows, Mac, and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Richard BustamanteGoogle Chrome

Dev Channel Update for Desktop

Tuesday, January 24, 2017

The dev channel has been updated to 57.0.2987.8 for Windows, Mac and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Krishna Govind Google Chrome

Dev Channel Update for Desktop

Thursday, January 19, 2017

The dev channel has been updated to 57.0.2986.0 for Windows, Mac and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Di Mu Google Chrome

Beta Channel Update for Chrome OS

Wednesday, January 18, 2017

hereforumfiling a bugFind out how Google Chrome

Beta Channel Update for Desktop

Wednesday, January 18, 2017

The beta channel has been updated to 56.0.2924.67 for Windows, Mac, and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Richard BustamanteGoogle Chrome

Dev Channel Update for Desktop

Tuesday, January 17, 2017

The dev channel has been updated to 57.0.2984.0 for Windows, Mac and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Di Mu Google Chrome

Dev Channel Update for Desktop

Thursday, January 12, 2017

The dev channel has been updated to 57.0.2979.0/2 for Windows, and 57.0.2979.0 for Mac and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Di Mu Google Chrome

Beta Channel Update for Chrome OS

Thursday, January 12, 2017

The Beta channel has been updated to 56.0.2924.58 (Platform version: 9000.58.0) for all Chrome OS devices. This build contains a number of bug fixes and security updates. Systems will be receiving updates over the next several days.

If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue...’ in the Chrome menu (3 vertical dots in the upper right corner of the browser).

Bernie Thompson

Google Chrome

Beta Channel Update for Desktop

Wednesday, January 11, 2017

The beta channel has been updated to 56.0.2924.59 for Windows, Mac, and Linux.

A partial list of changes is available in the log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Richard BustamanteGoogle Chrome

Chrome Releases

Dev Channel Update for Desktop

Dev Channel Update for Desktop

Beta Channel Update for Chrome OS

Stable Channel Update for Desktop

Beta Channel Update for Desktop

Dev Channel Update for Desktop

Dev Channel Update for Desktop

Beta Channel Update for Chrome OS

Beta Channel Update for Desktop

Dev Channel Update for Desktop

Dev Channel Update for Desktop

Beta Channel Update for Chrome OS

Beta Channel Update for Desktop

Labels

Archive