Google

Out of bounds read in WebGL in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to obtain potentially sens

Use after free in extensions in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially perform a

Use after free in offline mode in Google Chrome on iOS prior to 84.0.4147.125 allowed a remote attacker to potentially e

Use after free in Blink in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit heap co

Use after free in WebXR in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit heap co

Use after free in IndexedDB in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit hea

Use after free in media in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit heap co

Heap buffer overflow in Skia in Google Chrome prior to 84.0.4147.125 allowed a remote attacker who had compromised the r

Incorrect security UI in media in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially obtain s

Inappropriate implementation in installer in Google Chrome prior to 84.0.4147.125 allowed a local attacker to potentiall

Use after free in audio in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit heap co

Use after free in media in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit heap co

Use after free in task scheduling in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially explo

Use after free in ANGLE in Google Chrome prior to 84.0.4147.125 allowed a remote attacker to potentially exploit heap co

Use after free in WebUSB in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to potentially exploit heap c

Buffer overflow in Skia in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to potentially exploit heap co

Use after free in CSS in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to potentially exploit heap corr

Inappropriate implementation in WebView in Google Chrome on Android prior to 84.0.4147.105 allowed a remote attacker to

Type confusion in V8 in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to execute arbitrary code inside

Use after free in SCTP in Google Chrome prior to 84.0.4147.105 allowed a remote attacker to potentially exploit heap cor

Insufficient policy enforcement in extensions in Google Chrome prior to 85.0.4183.121 allowed an attacker who convinced

Type confusion in V8 in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially perform out of bou

Insufficient data validation in media in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially e

Insufficient policy enforcement in extensions in Google Chrome prior to 85.0.4183.121 allowed an attacker who convinced

Insufficient policy validation in serial in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentiall

Insufficient policy validation in extensions in Google Chrome prior to 85.0.4183.121 allowed an attacker who convinced a

Heap buffer overflow in storage in Google Chrome prior to 85.0.4183.121 allowed a remote attacker to potentially perform

Insufficient policy enforcement in networking in Google Chrome prior to 85.0.4183.102 allowed an attacker who convinced

In NetworkStackNotifier, there is a possible permissions bypass due to an unsafe implicit PendingIntent. This could lead

In netd, there is a possible out of bounds read due to a missing bounds check. This could lead to remote denial of servi

In NFC, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to local information discl

In NFC, there is a possible out of bounds read due to a missing bounds check. This could lead to remote information disc

In iptables, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalati

In NFC, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr

In NFC, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr

In Settings, there is a possible permissions bypass. This could lead to local information disclosure of the device's IME

In core networking, there is a missing permission check. This could lead to local information disclosure of app network

In NFC, there is a possible out of bounds write due to uninitialized data. This could lead to local escalation of privil

In NFC, there is a missing bounds check. This could lead to local information disclosure with System execution privilege

In NFC, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of pr

In Telephony, there is a missing permission check. This could lead to local information disclosure of radio data with no

In Zen Mode, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information

In NotificationManagerService, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to

In InputManagerService, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local i

In Settings, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information

In the Bluetooth server, there is a possible out of bounds write due to an integer overflow. This could lead to local es

In Settings, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information

In Settings, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information

In Settings, there is a possible permission bypass due to an unsafe PendingIntent. This could lead to local information