Summary: | <net-libs/webkit-gtk-2.20.2: Multiple vulnerabilities (WSA-2018-{0003,0004}) | ||
---|---|---|---|
Product: | Gentoo Security | Reporter: | GLSAMaker/CVETool Bot <glsamaker> |
Component: | Vulnerabilities | Assignee: | Gentoo Security <security> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gnome, ostroffjh, pedromoreno94 |
Priority: | Normal | Flags: | stable-bot:
sanity-check+
|
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | B2 [glsa+ cve] | ||
Package list: |
media-libs/woff2-1.0.2-r1
net-libs/webkit-gtk-2.20.3
|
Runtime testing required: | --- |
Bug Depends on: | 655550 | ||
Bug Blocks: | 658168 |
Description
GLSAMaker/CVETool Bot
![]() ------------------------------------------------------------------------ WebKitGTK+ Security Advisory WSA-2018-0004 ------------------------------------------------------------------------ Date reported : May 07, 2018 Advisory ID : WSA-2018-0004 Advisory URL : https://webkitgtk.org/security/WSA-2018-0004.html CVE identifiers : CVE-2018-4121, CVE-2018-4200, CVE-2018-4204. Several vulnerabilities were discovered in WebKitGTK+. CVE-2018-4121 Versions affected: WebKitGTK+ before 2.20.0. Credit to Natalie Silvanovich of Google Project Zero. Impact: Processing maliciously crafted web content may lead to arbitrary code execution. Description: Multiple memory corruption issues were addressed with improved memory handling. CVE-2018-4200 Versions affected: WebKitGTK+ before 2.20.2. Credit to Ivan Fratric of Google Project Zero. Impact: Processing maliciously crafted web content may lead to arbitrary code execution. Description: A memory corruption issue was addressed with improved state management. CVE-2018-4204 Versions affected: WebKitGTK+ before 2.20.1. Credit to Richard Zhu (fluorescence) working with Trend Micro's Zero Day Initiative, found by OSS-Fuzz. Impact: Processing maliciously crafted web content may lead to arbitrary code execution. Description: A memory corruption issue was addressed with improved memory handling. We recommend updating to the last stable version of WebKitGTK+. It is the best way of ensuring that you are running a safe version of WebKitGTK+. Please check our website for information about the last stable releases. Further information about WebKitGTK+ Security Advisories can be found at: https://webkitgtk.org/security.html The WebKitGTK+ team, May 07, 2018 Another batch coming up: https://webkitgtk.org/security/WSA-2018-0005.html Bump is done finally, but I'd prefer to let it simmer for a couple days in ~arch, as the upstream build system does something similar to chromium[jumbo-build] unconditionally now with some cmake dark magic and some ebuild things were reworked. So lets see what shakes out within 2-7 days. I can't find https://webkitgtk.org/security/WSA-2018-0003.html covered anywhere. Maybe include it here, and possibly also merge in the WSA-2018-0005 (bug 658168) stuff into the same bug here, as it's all the same version bump and stabling? Lets proceed with stabilization now then. x86@: you haven't done 661356 yet, so removing the bug depends and asking you to straight to stable it as security dep (older version was bundled in webkit-gtk before in earlier versions) x86 stable amd64 stable New GLSA request filed. This issue was resolved and addressed in GLSA 201808-04 at https://security.gentoo.org/glsa/201808-04 by GLSA coordinator Thomas Deutschmann (whissi). |