Summary
WebKitGTK is the port of the portable web rendering engine WebKit to the GTK platform.
Security Fix(es):
* webkitgtk: use-after-free issue leading to arbitrary code execution (CVE-2022-42826)
* webkitgtk: memory corruption issue leading to arbitrary code execution (CVE-2023-23517)
* webkitgtk: memory corruption issue leading to arbitrary code execution (CVE-2023-23518)
* webkitgtk: buffer overflow issue was addressed with improved memory handling (CVE-2022-32886)
* webkitgtk: out-of-bounds write issue was addressed with improved bounds checking (CVE-2022-32888)
* webkitgtk: correctness issue in the JIT was addressed with improved checks (CVE-2022-32923)
* webkitgtk: issue was addressed with improved UI handling (CVE-2022-42799)
* webkitgtk: type confusion issue leading to arbitrary code execution (CVE-2022-42823)
* webkitgtk: sensitive information disclosure issue (CVE-2022-42824)
* webkitgtk: memory disclosure issue was addressed with improved memory handling (CVE-2022-42852)
* webkitgtk: memory corruption issue leading to arbitrary code execution (CVE-2022-42863)
* webkitgtk: use-after-free issue leading to arbitrary code execution (CVE-2022-42867)
* webkitgtk: memory corruption issue leading to arbitrary code execution (CVE-2022-46691)
* webkitgtk: Same Origin Policy bypass issue (CVE-2022-46692)
* webkitgtk: logic issue leading to user information disclosure (CVE-2022-46698)
* webkitgtk: memory corruption issue leading to arbitrary code execution (CVE-2022-46699)
* webkitgtk: memory corruption issue leading to arbitrary code execution (CVE-2022-46700)
* webkitgtk: heap-use-after-free in WebCore::RenderLayer::addChild() (CVE-2023-25358)
* webkitgtk: heap-use-after-free in WebCore::RenderLayer::renderer() (CVE-2023-25360)
* webkitgtk: heap-use-after-free in WebCore::RenderLayer::setNextSibling() (CVE-2023-25361)
* webkitgtk: heap-use-after-free in WebCore::RenderLayer::repaintBlockSelectionGaps() (CVE-2023-25362)
* webkitgtk: heap-use-after-free in WebCore::RenderLayer::updateDescendantDependentFlags() (CVE-2023-25363)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the AlmaLinux Release Notes linked from the References section.
Fixed packages 4
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 9 | webkit2gtk3 | 2.38.5-1.el9 |
| AlmaLinux · 9 | webkit2gtk3-devel | 2.38.5-1.el9 |
| AlmaLinux · 9 | webkit2gtk3-jsc | 2.38.5-1.el9 |
| AlmaLinux · 9 | webkit2gtk3-jsc-devel | 2.38.5-1.el9 |
Vulnerabilities 22
-
High 8.8
A buffer overflow issue was addressed with improved memory handling. This issue is fixed in Safari 16, iOS 16, iOS 15.7…
-
High 8.8
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in macOS Big Sur 11.7, ma…
-
High 8.8
A type confusion issue was addressed with improved memory handling. This issue is fixed in tvOS 16.1, macOS Ventura 13,…
-
High 8.8
A memory corruption issue was addressed with improved state management. This issue is fixed in Safari 16.2, tvOS 16.2, …
-
High 8.8CVE-2022-42867 EPSS 35%
A use after free issue was addressed with improved memory management. This issue is fixed in Safari 16.2, tvOS 16.2, ma…
-
High 8.8
A memory consumption issue was addressed with improved memory handling. This issue is fixed in Safari 16.2, tvOS 16.2, …
-
High 8.8
A memory corruption issue was addressed with improved state management. This issue is fixed in Safari 16.2, tvOS 16.2, …
-
High 8.8
A memory corruption issue was addressed with improved input validation. This issue is fixed in Safari 16.2, tvOS 16.2, …
-
High 8.8
The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.3, macOS Ventura 13.2…
-
High 8.8
The issue was addressed with improved memory handling. This issue is fixed in macOS Monterey 12.6.3, macOS Ventura 13.2…
-
High 8.8
A use-after-free vulnerability in WebCore::RenderLayer::addChild in WebKitGTK before 2.36.8 allows attackers to execute…
-
High 8.8
A use-after-free vulnerability in WebCore::RenderLayer::renderer in WebKitGTK before 2.36.8 allows attackers to execute…
-
High 8.8
A use-after-free vulnerability in WebCore::RenderLayer::setNextSibling in WebKitGTK before 2.36.8 allows attackers to e…
-
Medium 6.5
A correctness issue in the JIT was addressed with improved checks. This issue is fixed in tvOS 16.1, iOS 15.7.1 and iPa…
-
Medium 6.5
The issue was addressed with improved memory handling. This issue is fixed in Safari 16.2, tvOS 16.2, macOS Ventura 13.…
-
Medium 6.5
A logic issue was addressed with improved checks. This issue is fixed in Safari 16.2, tvOS 16.2, iCloud for Windows 14.…
-
Medium 6.1
The issue was addressed with improved UI handling. This issue is fixed in tvOS 16.1, macOS Ventura 13, watchOS 9.1, Saf…
-
Medium 5.5
A logic issue was addressed with improved state management. This issue is fixed in tvOS 16.1, macOS Ventura 13, watchOS…
-
Medium 5.5
A logic issue was addressed with improved state management. This issue is fixed in Safari 16.2, tvOS 16.2, iCloud for W…
-
Unscored —
A use after free issue was addressed with improved memory management. This issue is fixed in macOS Ventura 13, iOS 16.1…
-
Unscored —
A use-after-free vulnerability in WebCore::RenderLayer::repaintBlockSelectionGaps in WebKitGTK before 2.36.8 allows att…
-
Unscored —
A use-after-free vulnerability in WebCore::RenderLayer::updateDescendantDependentFlags in WebKitGTK before 2.36.8 allow…
References
-
report
https://access.redhat.com/security/cve/CVE-2022-32886
-
report
https://access.redhat.com/security/cve/CVE-2022-32888
-
report
https://access.redhat.com/security/cve/CVE-2022-32923
-
report
https://access.redhat.com/security/cve/CVE-2022-42799
-
report
https://access.redhat.com/security/cve/CVE-2022-42823
-
report
https://access.redhat.com/security/cve/CVE-2022-42824
-
report
https://access.redhat.com/security/cve/CVE-2022-42826
-
report
https://access.redhat.com/security/cve/CVE-2022-42852
-
report
https://access.redhat.com/security/cve/CVE-2022-42863
-
report
https://access.redhat.com/security/cve/CVE-2022-42867
-
report
https://access.redhat.com/security/cve/CVE-2022-46691
-
report
https://access.redhat.com/security/cve/CVE-2022-46692
-
report
https://access.redhat.com/security/cve/CVE-2022-46698
-
report
https://access.redhat.com/security/cve/CVE-2022-46699
-
report
https://access.redhat.com/security/cve/CVE-2022-46700
-
report
https://access.redhat.com/security/cve/CVE-2023-23517
-
report
https://access.redhat.com/security/cve/CVE-2023-23518
-
report
https://access.redhat.com/security/cve/CVE-2023-25358
-
report
https://access.redhat.com/security/cve/CVE-2023-25360
-
report
https://access.redhat.com/security/cve/CVE-2023-25361
-
report
https://access.redhat.com/security/cve/CVE-2023-25362
-
report
https://access.redhat.com/security/cve/CVE-2023-25363
-
report
https://bugzilla.redhat.com/2128643
-
report
https://bugzilla.redhat.com/2140501
-
report
https://bugzilla.redhat.com/2140502
-
report
https://bugzilla.redhat.com/2140503
-
report
https://bugzilla.redhat.com/2140504
-
report
https://bugzilla.redhat.com/2140505
-
report
https://bugzilla.redhat.com/2156986
-
report
https://bugzilla.redhat.com/2156987
-
report
https://bugzilla.redhat.com/2156989
-
report
https://bugzilla.redhat.com/2156990
-
report
https://bugzilla.redhat.com/2156991
-
report
https://bugzilla.redhat.com/2156992
-
report
https://bugzilla.redhat.com/2156993
-
report
https://bugzilla.redhat.com/2156994
-
report
https://bugzilla.redhat.com/2167715
-
report
https://bugzilla.redhat.com/2167716
-
report
https://bugzilla.redhat.com/2167717