157 matches found
Arbitrary Code Execution
WebKitGTK+ is vulnerable to arbitrary code execution. Processing maliciously crafted web content may lead to arbitrary code execution...
webkitgtk: Out-of-bounds read leading to memory disclosure
An out-of-bounds read was addressed with improved input validation. This issue is fixed in iOS 12.3, macOS Mojave 10.14.5, tvOS 12.3, watchOS 5.2.1, Safari 12.1.1, iTunes for Windows 12.9.5, iCloud for Windows 7.12. Processing maliciously crafted web content may result in the disclosure of proces...
USN-4347-1 webkit2gtk vulnerability
A large number of security issues were discovered in the WebKitGTK Web and JavaScript engines. If a user were tricked into viewing a malicious website, a remote attacker could exploit a variety of issues related to web browser security, including cross-site scripting attacks, denial of service...
CVE-2020-11793
A use-after-free issue exists in WebKitGTK before 2.28.1 and WPE WebKit before 2.28.1 via crafted web content that allows remote attackers to execute arbitrary code or cause a denial of service memory corruption and application crash...
The vulnerability of the web page rendering modules in WebKitGTK and WPE WebKit allows a hacker to execute arbitrary code.
The vulnerability of the Web page rendering modules in WebKitGTK and WPE WebKit relates to the execution of operations beyond the buffer boundaries in memory. Exploiting this vulnerability allows a remote attacker to execute arbitrary code using a specially crafted web page or file...
Denial Of Service (DoS)
webkitgtk is vulnerable to denial of service DoS. The vulnerability exists through two array index errors, leading to out-of-bounds memory reads, were found in WebKit. Malicious web content could cause an application using WebKitGTK+ to crash...
Use-after-free
WebKitGTK+ is vulnerable to use-after-free. It allows remote attackers to execute arbitrary code or cause a denial of service application crash via vectors involving element focus...
Denial Of Service (DoS)
WebKitGTK+ is vulnerable to denial of service DoS. The attack is possible because it do not properly support the Ruby language, which allows attackers to cause a denial of service memory corruption or possibly have unspecified other impact via unknown vector...
Denial Of Service (DoS)
WebKitGTK+ is vulnerable to denial of service DoS. Due use-after-free flaws caused by vectors involving selections, malicious web content leads an application using WebKitGTK+ to crash or, potentially, execute arbitrary code with the privileges of the user running the application...
CVE-2020-10018
WebKitGTK through 2.26.4 and WPE WebKit through 2.26.4 which are the versions right before 2.28.0 contains a memory corruption issue use-after-free that may lead to arbitrary code execution. This issue has been fixed in 2.28.0 with improved memory handling...
CVE-2016-4761
WebKitGTK+ before 2.14.0: A use-after-free vulnerability can allow remote attackers to cause a DoS...
Design/Logic Flaw
WebKitGTK+ before 2.14.0: A use-after-free vulnerability can allow remote attackers to cause a DoS...
The vulnerability of the Web page rendering module in WebKitGTK+ lies in the lack of protection for service data, allowing attackers to gain unauthorized access to protected information.
The vulnerability of the WebPage rendering module in WebKitGTK+ relates to the lack of protection for service data. Exploiting this vulnerability can allow a malicious actor, operating remotely, to gain unauthorized access to protected information through a specially created web page...
webkitgtk: processing maliciously crafted web content lead to URI spoofing
WebKitGTK and WPE WebKit prior to version 2.24.1 are vulnerable to address bar spoofing upon certain JavaScript redirections. An attacker could cause malicious web content to be displayed as if for a trusted URI. This is similar to the CVE-2018-8383 issue in Microsoft Edge...
DEBIAN-CVE-2019-6251
WebKitGTK and WPE WebKit prior to version 2.24.1 are vulnerable to address bar spoofing upon certain JavaScript redirections. An attacker could cause malicious web content to be displayed as if for a trusted URI. This is similar to the CVE-2018-8383 issue in Microsoft Edge...