Bug 2040329 (CVE-2021-45482) - CVE-2021-45482 webkitgtk: use-after-free in WebCore::ContainerNode::firstChild
Summary: CVE-2021-45482 webkitgtk: use-after-free in WebCore::ContainerNode::firstChild
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2021-45482
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2040330 2041403 2041404
Blocks: 2040333
TreeView+ depends on / blocked
 
Reported: 2022-01-13 13:44 UTC by Guilherme de Almeida Suckevicz
Modified: 2022-05-17 09:44 UTC (History)
4 users (show)

Fixed In Version: webkitgtk 2.32.4
Doc Type: If docs needed, set a value
Doc Text:
A use-after-free vulnerability was found in webkitgtk. An attacker with network access could pass specially crafted HTML files causing an application to halt or crash.
Clone Of:
Environment:
Last Closed: 2022-05-10 22:45:27 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:1777 0 None None None 2022-05-10 13:23:36 UTC

Description Guilherme de Almeida Suckevicz 2022-01-13 13:44:25 UTC 
In WebKitGTK before 2.32.4, there is a use-after-free in WebCore::ContainerNode::firstChild, a different vulnerability than CVE-2021-30889.

Reference:
https://github.com/ChijinZ/security_advisories/tree/master/webkitgtk-2.32.3
Comment 1 Guilherme de Almeida Suckevicz 2022-01-13 13:44:40 UTC 
Created webkit2gtk3 tracking bugs for this issue:

Affects: fedora-all [bug 2040330]
Comment 4 errata-xmlrpc 2022-05-10 13:23:34 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2022:1777 https://access.redhat.com/errata/RHSA-2022:1777
Comment 5 Product Security DevOps Team 2022-05-10 22:45:25 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2021-45482
Note You need to log in before you can comment on or make changes to this bug.