Bug 2037481

Summary:	CVE-2022-0096 CVE-2022-0097 CVE-2022-0098 CVE-2022-0099 CVE-2022-0100 CVE-2022-0101 CVE-2022-0102 CVE-2022-0103 CVE-2022-0104 CVE-2022-0105 CVE-2022-0106 CVE-2022-0107 CVE-2022-0108 CVE-2022-0109 CVE-2022-0110 ... chromium: various flaws [fedora-all]
Product:	[Fedora] Fedora	Reporter:	msiddiqu
Component:	chromium	Assignee:	Tom "spot" Callaway <spotrh>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	35	CC:	spotrh, tpopela, yaneti
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	chromium-99.0.4844.51-1.fc35 chromium-99.0.4844.51-1.fc34 chromium-99.0.4844.51-1.fc36	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-11 14:45:07 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2037457, 2037458, 2037459, 2037460, 2037461, 2037462, 2037463, 2037464, 2037465, 2037466, 2037467, 2037468, 2037469, 2037470, 2037471, 2037472, 2037473, 2037474, 2037475, 2037476, 2037477, 2037478, 2037479, 2037480

Description msiddiqu 2022-01-05 17:20:38 UTC

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

Comment 1 msiddiqu 2022-01-05 17:20:40 UTC

Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.

=====

# bugfix, security, enhancement, newpackage (required)
type=security

# low, medium, high, urgent (required)
severity=urgent

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2037457,2037458,2037459,2037460,2037461,2037462,2037463,2037464,2037465,2037466,2037467,2037468,2037469,2037470,2037471,2037472,2037473,2037474,2037475,2037476,2037477,2037478,2037479,2037480,2037481

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Fedora Update System 2022-03-07 14:57:14 UTC

FEDORA-2022-49b52819a4 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-49b52819a4

Comment 3 Fedora Update System 2022-03-07 14:57:48 UTC

FEDORA-2022-d1a15f9cdb has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d1a15f9cdb

Comment 4 Fedora Update System 2022-03-07 14:58:22 UTC

FEDORA-2022-57923346cf has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-57923346cf

Comment 5 Fedora Update System 2022-03-07 15:51:46 UTC

FEDORA-2022-57923346cf has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-57923346cf`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-57923346cf

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-03-07 16:50:07 UTC

FEDORA-2022-49b52819a4 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-49b52819a4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-49b52819a4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-03-07 17:05:59 UTC

FEDORA-2022-d1a15f9cdb has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d1a15f9cdb`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d1a15f9cdb

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2022-03-11 14:45:07 UTC

FEDORA-2022-d1a15f9cdb has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-03-14 22:25:57 UTC

FEDORA-2022-49b52819a4 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2022-03-26 15:12:18 UTC

FEDORA-2022-57923346cf has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.