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

                                  CERT-Renater

                      Note d'Information No. 2021/VULN614
_____________________________________________________________________

DATE                : 18/11/2021

HARDWARE PLATFORM(S): /

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

=====================================================================
https://chromereleases.googleblog.com/2021/11/stable-channel-update-for-desktop.html
_____________________________________________________________________

Stable Channel Update for Desktop
Monday, November 15, 2021

The Chrome team is delighted to announce the promotion of Chrome 96 to
the stable channel for Windows, Mac and Linux. Chrome 96 is also
promoted to our new extended stable channel for Windows and Mac. This
will roll out over the coming days/weeks.

Chrome 96.0.4664.45 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
96.


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 25 security fixes. Below, we highlight fixes that
were contributed by external researchers. Please see the Chrome Security
Page for more information.


[$7500][1263620] High CVE-2021-38008: Use after free in media. Reported
by Marcin Towalski of Cisco Talos on 2021-10-26

[$2000][1260649] High CVE-2021-38009: Inappropriate implementation in
cache. Reported by Luan Herrera (@lbherrera_) on 2021-10-16

[$TBD][1240593] High CVE-2021-38006: Use after free in storage
foundation. Reported by Sergei Glazunov of Google Project Zero on
2021-08-17

[$TBD][1254189] High CVE-2021-38007: Type Confusion in V8. Reported by
Polaris Feng and SGFvamll at Singular Security Lab on 2021-09-29

[$TBD][1241091] High CVE-2021-38005: Use after free in loader. Reported
by Sergei Glazunov of Google Project Zero on 2021-08-18

[$TBD][1264477] High CVE-2021-38010: Inappropriate implementation in
service workers. Reported by Sergei Glazunov of Google Project Zero on
2021-10-28

[$TBD][1268274] High CVE-2021-38011: Use after free in storage
foundation. Reported by Sergei Glazunov of Google Project Zero on
2021-11-09

[$15000][1262791] Medium CVE-2021-38012: Type Confusion in V8. Reported
by Yonghwi Jin (@jinmo123) on 2021-10-24

[$10000][1242392] Medium CVE-2021-38013: Heap buffer overflow in
fingerprint recognition. Reported by raven (@raid_akame) on 2021-08-23

[$5000][1248567] Medium CVE-2021-38014: Out of bounds write in
Swiftshader. Reported by Atte Kettunen of OUSPG on 2021-09-10

[$3000][957553] Medium CVE-2021-38015: Inappropriate implementation in
input. Reported by David Erceg on 2019-04-29

[$3000][1244289] Medium CVE-2021-38016: Insufficient policy enforcement
in background fetch. Reported by Maurice Dauer  on 2021-08-28

[$2500][1256822] Medium CVE-2021-38017: Insufficient policy enforcement
in iframe sandbox. Reported by NDevTK on 2021-10-05

[$2000][1197889] Medium CVE-2021-38018: Inappropriate implementation in
navigation. Reported by Alesandro Ortiz on 2021-04-11

[$1000][1251179] Medium CVE-2021-38019: Insufficient policy enforcement
in CORS. Reported by Maurice Dauer on 2021-09-20

[$1000][1259694] Medium CVE-2021-38020: Insufficient policy enforcement
in contacts picker. Reported by Luan Herrera (@lbherrera_) on 2021-10-13

[$500][1233375] Medium CVE-2021-38021: Inappropriate implementation in
referrer. Reported by Prakash (@1lastBr3ath) and Jun Kokatsu on
2021-07-27

[$TBD][1248862] Low CVE-2021-38022: Inappropriate implementation in
WebAuthentication. Reported by Michal Kepkowski on 2021-09-13


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:

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

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


Interested in switching release channels?  Find out how here. 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.


Ben Mason
Google Chrome


=========================================================
+ 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 +
=========================================================