CVE-2022-1478 After free in SwiftShader allowed a remote attacker to exploit heap corruption.
This issue was addressed by disabling the webGL renderer. WebGL is currently not enabled by default in Google Chrome. If you are using an operating
CVE-2022-1482 Inappropriate implementation in Chrome prior to 101.0.4951.41 allowed a remote attacker to exploit heap corruption.
This issue has been fixed in WebGL in Google Chrome version 101.0.2 and later. CVE-2016-3075 There is a bug in WebGL in Google
CVE-2022-1499 Inappropriate implementation in Google Chrome prior to 101.0.4951.41 allowed a remote attacker to bypass same origin policy.
CVE-2017-5244 In the WebAuthn authenticator, the handling of unverified requests during the initial interaction flow has been improved. This issue is known as ' Interaction
CVE-2022-1487 An Ozone vulnerability in Chrome prior to 101.0.4951.41 could lead to heap corruption if a Wayland test is run.
CVE-2017-7517 was originally reported as a potential crash in the WebGL rendering engine. However, a later inspection revealed that it is actually a use after
CVE-2022-1634 After free in the Browser UI of Google Chrome prior to 101.0.4951.64 allowed a remote attacker to exploit heap corruption.
CVE-2018-4878 was discovered by Gary Steele. After the heap corruption occurs, the attacker can force the browser to crash or execute arbitrary code by triggering
Episode
00:00:00
00:00:00