Bug 2271868 - CVE-2024-2887 chromium: Type Confusion in WebAssembly [fedora-all]
Summary: CVE-2024-2887 chromium: Type Confusion in WebAssembly [fedora-all]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 39
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2024-2887
TreeView+ depends on / blocked
 
Reported: 2024-03-27 14:57 UTC by Mauro Matteo Cascella
Modified: 2024-03-29 02:41 UTC (History)
4 users (show)

Fixed In Version: chromium-123.0.6312.86-1.fc39 chromium-123.0.6312.86-1.fc38
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-03-29 01:10:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mauro Matteo Cascella 2024-03-27 14:57:25 UTC
More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2271866

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Mauro Matteo Cascella 2024-03-27 14:57:27 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=high

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2271866,2271868

# 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 2024-03-27 21:28:18 UTC
FEDORA-2024-b4dab205d7 (chromium-123.0.6312.86-1.fc38) has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b4dab205d7

Comment 3 Fedora Update System 2024-03-27 21:28:27 UTC
FEDORA-2024-0bb0e8f2a0 (chromium-123.0.6312.86-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-0bb0e8f2a0

Comment 4 Fedora Update System 2024-03-28 02:11:14 UTC
FEDORA-2024-0bb0e8f2a0 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-0bb0e8f2a0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0bb0e8f2a0

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

Comment 5 Fedora Update System 2024-03-28 03:25:02 UTC
FEDORA-2024-b4dab205d7 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-b4dab205d7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b4dab205d7

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

Comment 6 Fedora Update System 2024-03-29 01:10:35 UTC
FEDORA-2024-0bb0e8f2a0 (chromium-123.0.6312.86-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2024-03-29 02:41:55 UTC
FEDORA-2024-b4dab205d7 (chromium-123.0.6312.86-1.fc38) has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.