Hash: SHA256

             AUSCERT External Security Bulletin Redistribution

                     Stable Channel Update for Desktop
                              6 January 2022


        AusCERT Security Bulletin Summary

Product:           Google Chrome
Publisher:         Google
Operating System:  UNIX variants (UNIX, Linux, OSX)
Impact/Access:     Execute Arbitrary Code/Commands -- Remote with User Interaction
                   Denial of Service               -- Remote with User Interaction
                   Access Confidential Data        -- Remote with User Interaction
                   Reduced Security                -- Remote with User Interaction
Resolution:        Patch/Upgrade
CVE Names:         CVE-2022-0120 CVE-2022-0118 CVE-2022-0117
                   CVE-2022-0116 CVE-2022-0115 CVE-2022-0114
                   CVE-2022-0113 CVE-2022-0112 CVE-2022-0111
                   CVE-2022-0110 CVE-2022-0109 CVE-2022-0108
                   CVE-2022-0107 CVE-2022-0106 CVE-2022-0105
                   CVE-2022-0104 CVE-2022-0103 CVE-2022-0102
                   CVE-2022-0101 CVE-2022-0100 CVE-2022-0099
                   CVE-2022-0098 CVE-2022-0097 CVE-2022-0096

Original Bulletin: 

- --------------------------BEGIN INCLUDED TEXT--------------------

Stable Channel Update for Desktop

Tuesday, January 4, 2022

The Chrome team is delighted to announce the promotion of Chrome 97 to the
stable channel for Windows, Mac and Linux.This will roll out over the coming

Chrome 97.0.4692.71 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 97.

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

[$TBD][1275020] Critical CVE-2022-0096: Use after free in Storage. Reported by
Yangkang (@dnpushme) of 360 ATA on 2021-11-30

[$10000][1117173] High CVE-2022-0097: Inappropriate implementation in DevTools.
Reported by David Erceg on 2020-08-17

[$10000][1273609] High CVE-2022-0098: Use after free in Screen Capture. 
Reported by @ginggilBesel on 2021-11-24

[$5000][1245629] High CVE-2022-0099: Use after free in Sign-in. Reported by Rox
on 2021-09-01

[$TBD][1238209] High CVE-2022-0100: Heap buffer overflow in Media streams API. 
Reported by Cassidy Kim of Amber Security Lab, OPPO Mobile Telecommunications
Corp. Ltd. on 2021-08-10

[$TBD][1249426] High CVE-2022-0101: Heap buffer overflow in Bookmarks. Reported
by raven (@raid_akame)  on 2021-09-14

[$TBD][1260129] High CVE-2022-0102: Type Confusion in V8 . Reported by Brendon
Tiszka on 2021-10-14

[$TBD][1272266] High CVE-2022-0103: Use after free in SwiftShader. Reported by
Abraruddin Khan and Omair  on 2021-11-21

[$TBD][1273661] High CVE-2022-0104: Heap buffer overflow in ANGLE. Reported by
Abraruddin Khan and Omair on 2021-11-25

[$TBD][1274376] High CVE-2022-0105: Use after free in PDF. Reported by Cassidy
Kim of Amber Security Lab, OPPO Mobile Telecommunications Corp. Ltd. on

[$TBD][1278960] High CVE-2022-0106: Use after free in Autofill. Reported by
Khalil Zhani on 2021-12-10

[$10000][1248438] Medium CVE-2022-0107: Use after free in File Manager API. 
Reported by raven (@raid_akame)  on 2021-09-10

[$5000][1248444] Medium CVE-2022-0108: Inappropriate implementation in
Navigation. Reported by Luan Herrera (@lbherrera_) on 2021-09-10

[$4000][1261689] Medium CVE-2022-0109: Inappropriate implementation in
Autofill. Reported by Young Min Kim (@ylemkimon), CompSec Lab at Seoul National
University on 2021-10-20

[$3000][1237310] Medium CVE-2022-0110: Incorrect security UI in Autofill. 
Reported by Alesandro Ortiz on 2021-08-06

[$3000][1241188] Medium CVE-2022-0111: Inappropriate implementation in
Navigation. Reported by garygreen on 2021-08-18

[$3000][1255713] Medium CVE-2022-0112: Incorrect security UI in Browser UI. 
Reported by Thomas Orlita  on 2021-10-04

[$1000][1039885] Medium CVE-2022-0113: Inappropriate implementation in Blink. 
Reported by Luan Herrera (@lbherrera_) on 2020-01-07

[$TBD][1267627] Medium CVE-2022-0114: Out of bounds memory access in Web
Serial. Reported by Looben Yang on 2021-11-06

[$NA][1268903] Medium CVE-2022-0115: Uninitialized Use in File API. Reported by
Mark Brand of Google Project Zero on 2021-11-10

[$TBD][1272250] Medium CVE-2022-0116: Inappropriate implementation in
Compositing. Reported by Irvan Kurniawan (sourc7) on 2021-11-20

[$TBD][1115847] Low CVE-2022-0117: Policy bypass in Service Workers. Reported
by Dongsung Kim (@kid1ng) on 2020-08-13

[$TBD][1238631] Low CVE-2022-0118: Inappropriate implementation in WebShare. 
Reported by Alesandro Ortiz on 2021-08-11

[$TBD][1262953] Low CVE-2022-0120: Inappropriate implementation in Passwords. 
Reported by CHAKRAVARTHI (Ruler96) on 2021-10-25

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:

  o [1284397] 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.

Prudhvikumar Bommana
Google Chrome

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:


Australian Computer Emergency Response Team
The University of Queensland
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
Comment: http://www.auscert.org.au/render.html?it=1967