Bug 2092735 (CVE-2022-26717) - CVE-2022-26717 webkitgtk: Use-after-free leading to arbitrary code execution
Summary: CVE-2022-26717 webkitgtk: Use-after-free leading to arbitrary code execution
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-26717
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: 2092745 2092748 2092749
Blocks: 2092738
TreeView+ depends on / blocked
 
Reported: 2022-06-02 07:16 UTC by TEJ RATHI
Modified: 2022-12-06 06:21 UTC (History)
4 users (show)

Fixed In Version: webkitgtk 2.36.3
Clone Of:
Environment:
Last Closed: 2022-12-06 06:21:57 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:7704 0 None None None 2022-11-08 10:14:05 UTC
Red Hat Product Errata RHSA-2022:8054 0 None None None 2022-11-15 10:05:39 UTC

Description TEJ RATHI 2022-06-02 07:16:16 UTC 
Processing maliciously crafted web content may lead to arbitrary code execution. Description: A use after free issue was addressed with improved memory management.

Versions affected: WebKitGTK and WPE WebKit before 2.36.3.
Comment 1 Sandipan Roy 2022-06-02 07:35:07 UTC 
Created webkit2gtk3 tracking bugs for this issue:

Affects: fedora-all [bug 2092745]
Comment 3 errata-xmlrpc 2022-11-08 10:14:04 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2022:7704 https://access.redhat.com/errata/RHSA-2022:7704
Comment 4 errata-xmlrpc 2022-11-15 10:05:37 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2022:8054 https://access.redhat.com/errata/RHSA-2022:8054
Comment 5 Product Security DevOps Team 2022-12-06 06:21:56 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-2022-26717
Note You need to log in before you can comment on or make changes to this bug.