Stable Channel Update


The Chrome team is delighted to announce the promotion of Chrome 52 to the stable channel for Windows, Mac and Linux. Chrome 52.0.2743.82 contains a number of fixes and improvements -- a list of changes is available in the[ log](<https://chromium.googlesource.com/chromium/src/+log/51.0.2704.106..52.0.2743.82?pretty=fuller&n=10000>). Watch out for upcoming[ Chrome](<http://chrome.blogspot.com/>) and[ Chromium](<http://blog.chromium.org/>) blog posts about new features and big efforts delivered in 52. #### 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 [48 security fixes](<https://bugs.chromium.org/p/chromium/issues/list?can=1&q=label%3ARelease-0-M52>). Below, we highlight fixes that were contributed by external researchers. Please see the [Chromium security page](<http://sites.google.com/a/chromium.org/dev/Home/chromium-security>) for more information. [$15000][[610600](<https://crbug.com/610600>)] **High** CVE-2016-1706: Sandbox escape in PPAPI. Credit to Pinkie Pie [$3000][[622183](<https://crbug.com/622183>)] **High** CVE-2016-1707: URL spoofing on iOS. Credit to xisigr of Tencent's Xuanwu Lab [$500][[613949](<https://crbug.com/613949>)] **High** CVE-2016-1708: Use-after-free in Extensions. Credit to Adam Varsan [$500][[614934](<https://crbug.com/614934>)] **High** CVE-2016-1709: Heap-buffer-overflow in sfntly. Credit to ChenQin of Topsec Security Team [$8000][[616907](<https://crbug.com/616907>)] **High** CVE-2016-1710: Same-origin bypass in Blink. Credit to Mariusz Mlynski [$7500][[617495](<https://crbug.com/617495>)] **High** CVE-2016-1711: Same-origin bypass in Blink. Credit to Mariusz Mlynski [$3000][[618237](<https://crbug.com/618237>)] **High** CVE-2016-5127: Use-after-free in Blink. Credit to cloudfuzzer [$7500][[619166](<https://crbug.com/619166>)] **High** CVE-2016-5128: Same-origin bypass in V8. Credit to Anonymous [$5000][[620553](<https://crbug.com/620553>)] **High** CVE-2016-5129: Memory corruption in V8. Credit to Jeonghoon Shin [$2000][[623319](<https://crbug.com/623319>)] **High** CVE-2016-5130: URL spoofing. Credit to Wadih Matar [$3500][[623378](<https://crbug.com/623378>)] **High** CVE-2016-5131: Use-after-free in libxml. Credit to Nick Wellnhofer [$1000][[607543](<https://crbug.com/607543>)] **Medium** CVE-2016-5132: Limited same-origin bypass in Service Workers. Credit to Ben Kelly [$1000][[613626](<https://crbug.com/613626>)] **Medium** CVE-2016-5133: Origin confusion in proxy authentication. Credit to Patch Eudor [$500][[593759](<https://crbug.com/593759>)] **Medium** CVE-2016-5134: URL leakage via PAC script. Credit to Alex Chapman and Paul Stone of Context Information Security [$500][[605451](<https://crbug.com/605451>)] **Medium** CVE-2016-5135: Content-Security-Policy bypass. Credit to ShenYeYinJiu of Tencent Security Response Center, TSRC [$1000][[625393](<https://crbug.com/625393>)] **Medium** CVE-2016-5136: Use after free in extensions. Credit to Rob Wu [$1000][[625945](<https://crbug.com/625945>)] **Medium** CVE-2016-5137: History sniffing with HSTS and CSP. Credit to Xiaoyin Liu 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: [[629852](<https://crbug.com/629852>)] CVE-2016-1705: Various fixes from internal audits, fuzzing and other initiatives. Many of our security bugs are detected using [AddressSanitizer](<http://code.google.com/p/address-sanitizer/wiki/AddressSanitizer>), [MemorySanitizer](<https://code.google.com/p/memory-sanitizer/wiki/MemorySanitizer>), [Control Flow Integrity](<https://sites.google.com/a/chromium.org/dev/developers/testing/control-flow-integrity>) or [LibFuzzer](<https://sites.google.com/a/chromium.org/dev/developers/testing/libfuzzer>). Interested in switching release channels?[ Find out how](<http://www.chromium.org/getting-involved/dev-channel>). If you find a new issue, please let us know by[ filing a bug](<http://crbug.com/>). The [community help forum](<https://productforums.google.com/forum/#!forum/chrome>) is also a great place to reach out for help or learn about common issues. Krishna Govind Google Chrome

Affected Software

CPE Name Name Version
google chrome 52.0.2743.82