WebKitGTK and WPE WebKit Security Advisory WSA-2019-0002

• Date Reported: April 10, 2019

• Advisory ID: WSA-2019-0002

• CVE identifiers: CVE-2019-6201, CVE-2019-6251, CVE-2019-7285, CVE-2019-7292, CVE-2019-8503, CVE-2019-8506, CVE-2019-8515, CVE-2019-8518, CVE-2019-8523, CVE-2019-8524, CVE-2019-8535, CVE-2019-8536, CVE-2019-8544, CVE-2019-8551, CVE-2019-8558, CVE-2019-8559, CVE-2019-8563, CVE-2019-11070.

Several vulnerabilities were discovered in WebKitGTK and WPE WebKit.

• CVE-2019-6201

  • Versions affected: WebKitGTK before 2.22.6 and WPE WebKit before 2.22.4.
  • Credit to dwfault working with ADLab of Venustech.
  • Processing maliciously crafted web content may lead to arbitrary code execution. Multiple memory corruption issues were addressed with improved memory handling.

• CVE-2019-6251

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.1.
  • Credit to Dhiraj.
  • Processing maliciously crafted web content may lead to spoofing. WebKitGTK and WPE WebKit were vulnerable to a URI spoofing attack similar to the CVE-2018-8383 issue in Microsoft Edge.

• CVE-2019-7285

  • Versions affected: WebKitGTK before 2.22.6 and WPE WebKit before 2.22.4.
  • Credit to dwfault working at ADLab of Venustech.
  • Processing maliciously crafted web content may lead to arbitrary code execution. A use after free issue was addressed with improved memory management.

• CVE-2019-7292

  • Versions affected: WebKitGTK before 2.22.6 and WPE WebKit before 2.22.4.
  • Credit to Zhunki and Zhiyi Zhang of 360 ESG Codesafe Team.
  • Processing maliciously crafted web content may result in the disclosure of process memory. A validation issue was addressed with improved logic.

• CVE-2019-8503

  • Versions affected: WebKitGTK before 2.22.6 and WPE WebKit before 2.22.4.
  • Credit to Linus Särud of Detectify.
  • A malicious website may be able to execute scripts in the context of another website. A logic issue was addressed with improved validation.

• CVE-2019-8506

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Samuel Groß of Google Project Zero.
  • Processing maliciously crafted web content may lead to arbitrary code execution. A type confusion issue was addressed with improved memory handling.

• CVE-2019-8515

  • Versions affected: WebKitGTK before 2.22.6 and WPE WebKit before 2.22.4.
  • Credit to James Lee, @Windowsrcer.
  • Processing maliciously crafted web content may disclose sensitive user information. A cross-origin issue existed with the fetch API. This was addressed with improved input validation.

• CVE-2019-8518

  • Versions affected: WebKitGTK before 2.22.7 and WPE WebKit before 2.22.5.
  • Credit to Samuel Groß 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-2019-8523

  • Versions affected: WebKitGTK before 2.22.7 and WPE WebKit before 2.22.5.
  • Credit to Apple.
  • Processing maliciously crafted web content may lead to arbitrary code execution. Multiple memory corruption issues were addressed with improved memory handling.

• CVE-2019-8524

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to G. Geshev working with Trend Micro 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-2019-8535

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Zhiyang Zeng, @Wester, of Tencent Blade Team.
  • Processing maliciously crafted web content may lead to arbitrary code execution. A memory corruption issue was addressed with improved state management.

• CVE-2019-8536

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Apple.
  • Processing maliciously crafted web content may lead to arbitrary code execution. A memory corruption issue was addressed with improved memory handling.

• CVE-2019-8544

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to an anonymous researcher.
  • Processing maliciously crafted web content may lead to arbitrary code execution. A memory corruption issue was addressed with improved memory handling.

• CVE-2019-8551

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Ryan Pickren, ryanpickren.com.
  • Processing maliciously crafted web content may lead to universal cross site scripting. A logic issue was addressed with improved validation.

• CVE-2019-8558

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Samuel Groß 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-2019-8559

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Apple.
  • Processing maliciously crafted web content may lead to arbitrary code execution. Multiple memory corruption issues were addressed with improved memory handling.

• CVE-2019-8563

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.0.
  • Credit to Apple.
  • Processing maliciously crafted web content may lead to arbitrary code execution. Multiple memory corruption issues were addressed with improved memory handling.

• CVE-2019-11070

  • Versions affected: WebKitGTK and WPE WebKit before 2.24.1.
  • Credit to Igalia.
  • WebKitGTK and WPE WebKit failed to properly apply configured HTTP proxy settings when downloading livestream video (HLS, DASH, or Smooth Streaming), an error resulting in deanonymization. This issue was corrected by changing the way livestreams are downloaded.

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: https://webkitgtk.org/security.html or https://wpewebkit.org/security/.