====================================================================

                               CERT-Renater

                  Note d'Information No. 2017/VULN025
_____________________________________________________________________

DATE                : 27/01/2017

HARDWARE PLATFORM(S): /

OPERATING SYSTEM(S): Systems running Chrome versions prior to
                                  56.0.2924.76.

=====================================================================
https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-desktop.html
____________________________________________________________________

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)
[$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 danberm
[$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 李普君 of 无声信息技术PKAV Team
[$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


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

==========================================================
Serveur de référence du CERT-Renater
https://services.renater.fr/ssi/
==========================================================
+ CERT-RENATER          | tel : 01-53-94-20-44           +
+ 23 - 25 Rue Daviel    | fax : 01-53-94-20-41           +
+ 75013 Paris           | email: cert@support.renater.fr +
==========================================================