WebKitGTK+ and WPE WebKit Security Advisory WSA-2018-0007

                							

            -----------------------------------------------------------------------
WebKitGTK+ and WPE WebKit Security Advisory                WSA-2018-0007
------------------------------------------------------------------------

Date reported           : September 26, 2018
Advisory ID             : WSA-2018-0007
<p>CVE identifiers         : CVE-2018-4207, CVE-2018-4208, CVE-2018-4209,
                         CVE-2018-4210, CVE-2018-4212, CVE-2018-4213,
                         CVE-2018-4191, CVE-2018-4197, CVE-2018-4299,
                         CVE-2018-4306, CVE-2018-4309, CVE-2018-4311,
                         CVE-2018-4312, CVE-2018-4314, CVE-2018-4315,
                         CVE-2018-4316, CVE-2018-4317, CVE-2018-4318,
                         CVE-2018-4319, CVE-2018-4323, CVE-2018-4328,
                         CVE-2018-4358, CVE-2018-4359, CVE-2018-4361.

Several vulnerabilities were discovered in WebKitGTK+ and WPE WebKit.

CVE-2018-4207
   Versions affected: WebKitGTK+ before 2.20.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. This issue was
   addressed with improved checks.

CVE-2018-4208
   Versions affected: WebKitGTK+ before 2.20.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. This issue was
   addressed with improved checks.

CVE-2018-4209
   Versions affected: WebKitGTK+ before 2.20.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. This issue was
   addressed with improved checks.

CVE-2018-4210
   Versions affected: WebKitGTK+ before 2.20.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction with indexing types caused a failure. An
   array indexing issue existed in the handling of a function in
   JavaScriptCore. This issue was addressed with improved checks.

CVE-2018-4212
   Versions affected: WebKitGTK+ before 2.20.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. This issue was
   addressed with improved checks.

CVE-2018-4213
   Versions affected: WebKitGTK+ before 2.20.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. This issue was
   addressed with improved checks.

CVE-2018-4191
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. A memory corruption
   issue was addressed with improved validation.

CVE-2018-4197
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4299
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Samuel Groβ (saelo) working with Trend Micro's Zero Day
   Initiative.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. Multiple memory corruption issues were addressed
   with improved memory handling.

CVE-2018-4306
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4309
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to an anonymous researcher working with Trend Micro's Zero
   Day Initiative.
   A malicious website may be able to execute scripts in the context of
   another website. A cross-site scripting issue existed in WebKit.
   This issue was addressed with improved URL validation.

CVE-2018-4311
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Erling Alf Ellingsen (@steike).
   Cross-origin SecurityErrors includes the accessed frame’s origin.
   The issue was addressed by removing origin information.

CVE-2018-4312
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4314
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4315
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4316
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to crixer, Hanming Zhang (@4shitak4) of Qihoo 360 Vulcan
   Team.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A memory corruption issue was addressed with
   improved state management.

CVE-2018-4317
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4318
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. A use after free issue was addressed with improved
   memory management.

CVE-2018-4319
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to John Pettitt of Google.
   A malicious website may cause unexepected cross-origin behavior. A
   cross-origin issue existed with iframe elements. This was addressed
   with improved tracking of security origins.

CVE-2018-4323
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. Multiple memory corruption issues were addressed
   with improved memory handling.

CVE-2018-4328
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Ivan Fratric of Google Project Zero.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. Multiple memory corruption issues were addressed
   with improved memory handling.

CVE-2018-4358
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to @phoenhex team (@bkth_ @5aelo @_niklasb) working with
   Trend Micro's Zero Day Initiative.
   Processing maliciously crafted web content may lead to arbitrary
   code execution. Multiple memory corruption issues were addressed
   with improved memory handling.

CVE-2018-4359
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Samuel Groß (@5aelo).
   Processing maliciously crafted web content may lead to arbitrary
   code execution. Multiple memory corruption issues were addressed
   with improved memory handling.

CVE-2018-4361
   Versions affected: WebKitGTK+ and WPE WebKit before 2.22.0.
   Credit to Google OSS-Fuzz.
   Unexpected interaction causes an ASSERT failure. A memory corruption
   issue was addressed with improved memory handling.


We recommend updating to the latest stable versions of WebKitGTK+ and
WPE WebKit. It is the best way to ensure that you are running safe
versions of WebKit. Please check our websites for information about the
latest stable releases.

Further information about WebKitGTK+ and WPE WebKit security advisories
can be found at: <a rel="nofollow" href="https://webkitgtk.org/security.html">https://webkitgtk.org/security.html</a> or
<a rel="nofollow" href="https://wpewebkit.org/security/">https://wpewebkit.org/security/</a>.

The WebKitGTK+ and WPE WebKit team,
September 26, 2018

<p>