Bug 2156990 (CVE-2022-46691) - CVE-2022-46691 webkitgtk: memory corruption issue leading to arbitrary code execution
Summary: CVE-2022-46691 webkitgtk: memory corruption issue leading to arbitrary code e...
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2022-46691
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: 2189092 2189093
Blocks: 2156747
TreeView+ depends on / blocked
 
Reported: 2022-12-30 05:25 UTC by TEJ RATHI
Modified: 2023-05-16 08:18 UTC (History)
2 users (show)

Fixed In Version: WebKitGTK 2.38.3
Clone Of:
Environment:
Last Closed: 2022-12-31 02:01:18 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:2256 0 None None None 2023-05-09 07:22:56 UTC
Red Hat Product Errata RHSA-2023:2834 0 None None None 2023-05-16 08:18:13 UTC

Description TEJ RATHI 2022-12-30 05:25:36 UTC 
Processing maliciously crafted web content may lead to arbitrary code execution. Description: A memory consumption issue was addressed with improved memory handling.

Versions affected: WebKitGTK and WPE WebKit before 2.38.1.
Comment 1 TEJ RATHI 2022-12-30 05:48:42 UTC 
Upstream Security Advisory:
https://webkitgtk.org/security/WSA-2022-0011.html
Comment 2 Product Security DevOps Team 2022-12-31 02:01:16 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-46691
Comment 4 errata-xmlrpc 2023-05-09 07:22:55 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2023:2256 https://access.redhat.com/errata/RHSA-2023:2256
Comment 5 errata-xmlrpc 2023-05-16 08:18:12 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2023:2834 https://access.redhat.com/errata/RHSA-2023:2834
Note You need to log in before you can comment on or make changes to this bug.