Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

Google

16,977 known vulnerabilities

981
CRITICAL
5,879
HIGH
5,898
MEDIUM
447
LOW

Top Products

android 8109 chrome 4748 tensorflow 431 chrome os 215 asylo 16 blink 12 mcp toolbox for databases 9 linux and chrome os 8 gvisor 7 fuchsia 6
13,206 CVEs · Page 138/265
7.8
CVE-2022-20274

In Keyguard, there is a missing permission check. This could lead to local escalation of privilege and prevention of scr

6.5
CVE-2022-20273

In Bluetooth, there is a possible out of bounds read due to a heap buffer overflow. This could lead to remote informatio

5.5
CVE-2022-20272

In PermissionController, there is a possible misunderstanding about the default SMS application's permission set due to

7.8
CVE-2022-20271

In PermissionController, there is a possible way to grant some permissions without user consent due to misleading or ins

5.5
CVE-2022-20270

In Content, there is a possible way to learn gmail account name on the device due to a permissions bypass. This could le

6.8
CVE-2022-20269

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

7.8
CVE-2022-20268

In RestrictionsManager, there is a possible way to send a broadcast that should be restricted to system apps due to a pe

3.3
CVE-2022-20267

In bluetooth, there is a possible way to enable or disable bluetooth connection without user consent due to a missing pe

5.0
CVE-2022-20266

In Companion, there is a possible way to keep a service running with elevated importance without showing foreground serv

4.6
CVE-2022-20265

In Settings, there is a possible way to bypass factory reset permissions due to a permissions bypass. This could lead to

5.5
CVE-2022-20263

In ActivityManager, there is a way to read process state for other users due to a missing permission check. This could l

3.3
CVE-2022-20262

In ActivityManager, there is a possible way to check another process's capabilities due to a missing permission check. T

2.3
CVE-2022-20261

In LocationManager, there is a possible way to get location information due to a missing permission check. This could le

5.5
CVE-2022-20260

In the Phone app, there is a possible crash loop due to resource exhaustion. This could lead to local persistent denial

5.5
CVE-2022-20259

In Telephony, there is a possible leak of ICCID and EID due to a missing permission check. This could lead to local info

7.8
CVE-2022-20258

In Bluetooth, there is a possible way to bypass compiler exploit mitigations due to a configuration error. This could le

3.3
CVE-2022-20257

In Bluetooth, there is a possible way to pair a display only device without PIN confirmation due to a logic error in the

6.4
CVE-2022-20256

In the Audio HAL, there is a possible out of bounds write due to a race condition. This could lead to local escalation o

4.4
CVE-2022-20255

In SettingsProvider, there is a possible way to read or change the default ringtone due to a missing permission check. T

8.8
CVE-2022-20254

In Wi-Fi, there is a permissions bypass. This could lead to local escalation of privilege from the guest user with no ad

6.5
CVE-2022-20253

In Bluetooth, there is a possible cleanup failure due to an uncaught exception. This could lead to remote denial of serv

6.1
CVE-2022-2390

Apps developed with Google Play Services SDK incorrectly had the mutability flag set to PendingIntents that were passed

7.5
CVE-2022-20408

Product: AndroidVersions: Android kernelAndroid ID: A-204782372References: N/A

7.5
CVE-2022-20407

Product: AndroidVersions: Android kernelAndroid ID: A-210916981References: N/A

7.5
CVE-2022-20406

Product: AndroidVersions: Android kernelAndroid ID: A-184676385References: N/A

9.8
CVE-2022-20405

Product: AndroidVersions: Android kernelAndroid ID: A-216363416References: N/A

7.5
CVE-2022-20404

Product: AndroidVersions: Android kernelAndroid ID: A-205714161References: N/A

9.8
CVE-2022-20403

Product: AndroidVersions: Android kernelAndroid ID: A-207975764References: N/A

9.8
CVE-2022-20402

Product: AndroidVersions: Android kernelAndroid ID: A-218701042References: N/A

7.5
CVE-2022-20401

In SAEMM_RetrievEPLMNList of SAEMM_ContextManagement.c, there is a possible out of bounds read due to a missing bounds c

9.8
CVE-2022-20400

In cd_CodeMsg of cd_codec.c, there is a possible out of bounds write due to a missing bounds check. This could lead to r

9.8
CVE-2022-20384

Product: AndroidVersions: Android kernelAndroid ID: A-211727306References: N/A

7.8
CVE-2022-20383

In AllocateInternalBuffers of g3aa_buffer_allocator.cc, there is a possible out of bounds write due to an integer overfl

6.7
CVE-2022-20382

In (TBD) of (TBD), there is a possible out of bounds write due to kernel stack overflow. This could lead to local escala

9.8
CVE-2022-20381

Product: AndroidVersions: Android kernelAndroid ID: A-188935887References: N/A

7.5
CVE-2022-20380

Product: AndroidVersions: Android kernelAndroid ID: A-212625740References: N/A

6.7
CVE-2022-20379

In lwis_buffer_alloc of lwis_buffer.c, there is a possible arbitrary code execution due to a use after free. This could

9.8
CVE-2022-20378

Product: AndroidVersions: Android kernelAndroid ID: A-234657153References: N/A

6.7
CVE-2022-20377

In TBD of keymaster_ipc.cpp, there is a possible to force gatekeeper, fingerprint, and faceauth to use a known HMAC key.

6.7
CVE-2022-20376

In trusty_log_seq_start of trusty-log.c, there is a possible use after free due to improper locking. This could lead to

7.5
CVE-2022-20375

In LteRrcNrProAsnDecode of LteRrcNr_Codec.c, there is a possible out of bounds read due to a missing bounds check. This

6.4
CVE-2022-20373

In st21nfc_loc_set_polaritymode of fc/st21nfc.c, there is a possible use after free due to a race condition. This could

6.7
CVE-2022-20372

In exynos5_i2c_irq of (TBD), there is a possible out of bounds write due to a use after free. This could lead to local e

6.4
CVE-2022-20371

In dm_bow_dtr and related functions of dm-bow.c, there is a possible use after free due to a race condition. This could

7.5
CVE-2022-20370

Product: AndroidVersions: Android kernelAndroid ID: A-215730643References: N/A

6.7
CVE-2022-20369

In v4l2_m2m_querybuf of v4l2-mem2mem.c, there is a possible out of bounds write due to improper input validation. This c

7.8
CVE-2022-20368

Product: AndroidVersions: Android kernelAndroid ID: A-224546354References: Upstream kernel

6.7
CVE-2022-20367

In construct_transaction of lwis_ioctl.c, there is a possible out of bounds write due to an integer overflow. This could

6.7
CVE-2022-20366

In ioctl_dpm_clk_update of lwis_ioctl.c, there is a possible out of bounds write due to an integer overflow. This could

9.8
CVE-2022-20365

Product: AndroidVersions: Android kernelAndroid ID: A-229632566References: N/A

Frequently Asked Questions

How many CVEs affect Google?

Google has 16,977 CVE records in our database, including 1160 critical and 8152 high severity vulnerabilities. 94 of these are listed in CISA's Known Exploited Vulnerabilities catalog.

What are the most severe Google vulnerabilities?

Google has 1160 critical severity (CVSS 9.0+) and 8152 high severity (CVSS 7.0-8.9) vulnerabilities. 94 vulnerabilities are confirmed as actively exploited in the wild.

How can I scan for Google vulnerabilities?

CyberStrike's AI-powered security agents automatically detect vulnerabilities in Google products across your infrastructure. The platform provides continuous pentesting, DAST scanning, and real-time vulnerability monitoring with actionable remediation guidance.

Detect Google Vulnerabilities

CyberStrike scans your infrastructure for Google vulnerabilities and provides real-time remediation guidance.

Get Started