Bug 2082548 (CVE-2022-30293) - CVE-2022-30293 webkitgtk: heap-buffer-overflow in WebCore::TextureMapperLayer::setContentsLayer
Summary: CVE-2022-30293 webkitgtk: heap-buffer-overflow in WebCore::TextureMapperLayer...
Keywords:
Status: NEW
Alias: CVE-2022-30293
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:
: CVE-2022-30294 (view as bug list)
Depends On: 2082550 2083011 2083012 2082549 2082551
Blocks: 2082555
TreeView+ depends on / blocked
 
Reported: 2022-05-06 12:07 UTC by Avinash Hanwate
Modified: 2022-06-06 10:45 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
A heap buffer overflow vulnerability was found in WebKitGTK. The vulnerability occurs when processing or rendering HTML content in WebKit. This flaw allows a remote attacker to trick the victim into opening a specially crafted web page, triggering a heap buffer overflow error and leading to the execution of arbitrary code on the system.
Clone Of:
Environment:
Last Closed:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Avinash Hanwate 2022-05-06 12:07:10 UTC 
In WebKitGTK through 2.36.0 (and WPE WebKit), there is a heap-based buffer overflow in WebCore::TextureMapperLayer::setContentsLayer in WebCore/platform/graphics/texmap/TextureMapperLayer.cpp.

https://github.com/ChijinZ/security_advisories/tree/master/webkitgtk-2.36.0
https://bugs.webkit.org/show_bug.cgi?id=237187
Comment 1 Avinash Hanwate 2022-05-06 12:07:47 UTC 
Created gnucash tracking bugs for this issue:

Affects: epel-all [bug 2082549]


Created pywebkitgtk tracking bugs for this issue:

Affects: epel-all [bug 2082550]


Created webkit2gtk3 tracking bugs for this issue:

Affects: fedora-all [bug 2082551]
Comment 2 Sandipan Roy 2022-05-09 05:43:22 UTC 
*** Bug 2082544 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.