Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#11925 closed enhancement (fixed)

webkitgtk-2.24.1 (CVE-2019-6251)

Reported by: Douglas R. Reno Owned by: Douglas R. Reno
Priority: high Milestone: 9.0
Component: BOOK Version: SVN
Severity: normal Keywords:


New point versions

What's new in the WebKitGTK 2.24.1 release?

  - Do not allow changes in active URI before provisional load starts for non-API requests.
  - Stop the threaded compositor when the page is not visible or layer tree state is frozen.
  - Use WebKit HTTP source element again for adaptive streaming fragments downloading.
  - Properly handle empty resources in webkit_web_resource_get_data().
  - Add quirk to ensure uses the modern UI.
  - Fix methods returing GObject or boxed types in JavaScriptCore GLib API.
  - Ensure callback data is passed to functions and constructors with no parameters in JavaScriptCore GLib API.
  - Fix rendering of complex text when the font uses x,y origins.
  - Fix sound loop with Google Hangouts and WhatsApp notifications.
  - Fix the build with GStreamer 1.12.5 and GST GL enabled.
  - Detect SSE2 at compile time.
  - Fix several crashes and rendering issues.
  - Security fixes: CVE-2019-6251.

Change History (5)

comment:1 by Douglas R. Reno, 5 years ago

Owner: changed from blfs-book to Douglas R. Reno
Status: newassigned

comment:2 by Douglas R. Reno, 5 years ago

Priority: normalhigh

comment:3 by Douglas R. Reno, 5 years ago


    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.

    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.

comment:4 by Douglas R. Reno, 5 years ago

Resolution: fixed
Status: assignedclosed

Fixed at r21546

comment:5 by Bruce Dubbs, 4 years ago

Milestone: 8.59.0

Milestone renamed

Note: See TracTickets for help on using tickets.