Menu

Star on GitHub · 3.2k

2022

25,043 vulnerabilities published in 2022.

Results

25,043· Page 197/501
5.5
CVE-2022-20332

In PackageManager, there is a possible way to determine whether an app is installed, without query permissions, due to s

7.8
CVE-2022-20331

In the Framework, there is a possible way to enable a work profile without user consent due to a tapjacking/overlay atta

3.5
CVE-2022-20330

In Bluetooth, there is a possible way to connect or disconnect bluetooth devices without user awareness due to a missing

7.8
CVE-2022-20329

In Wifi, there is a possible way to enable Wifi without permissions due to a missing permission check. This could lead t

3.3
CVE-2022-20328

In PackageManager, there is a possible way to determine whether an app is installed due to a missing permission check. T

2.8
CVE-2022-20327

In Wi-Fi, there is a possible way to retrieve the WiFi SSID without location permissions due to a missing permission che

5.5
CVE-2022-20326

In Telephony, there is a possible disclosure of SIM identifiers due to a missing permission check. This could lead to lo

7.8
CVE-2022-20325

In Media, there is a possible code execution due to a use after free. This could lead to local escalation of privilege w

5.5
CVE-2022-20324

In Framework, there is a possible way to determine whether an app is installed, without query permissions, due to side c

5.5
CVE-2022-20323

In PackageManager, there is a possible package installation disclosure due to a missing permission check. This could lea

5.5
CVE-2022-20322

In PackageManager, there is a possible installed package disclosure due to a missing permission check. This could lead t

3.3
CVE-2022-20321

In Settings, there is a possible way for an application without permissions to read content of WiFi QR codes due to a mi

3.3
CVE-2022-20320

In ActivityManager, there is a possible way to determine whether an app is installed, without query permissions, due to

7.8
CVE-2022-20319

In DreamServices, there is a possible way to launch arbitrary protected activities due to a confused deputy. This could

3.3
CVE-2022-20318

In PackageInstaller, there is a possible way to determine whether an app is installed, without query permissions, due to

5.5
CVE-2022-20317

In SystemUI, there is a possible way to unexpectedly enable the external speaker due to a logic error in the code. This

3.3
CVE-2022-20316

In ContentResolver, there is a possible way to determine whether an app is installed, without query permissions, due to

3.3
CVE-2022-20315

In ActivityManager, there is a possible disclosure of installed packages due to a missing permission check. This could l

6.7
CVE-2022-20314

In KeyChain, there is a possible spoof keychain chooser activity request due to improper input validation. This could le

6.8
CVE-2022-20313

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

5.5
CVE-2022-20312

In WifiP2pManager, there is a possible toobtain WiFi P2P MAC address without user consent due to missing permission chec

3.3
CVE-2022-20311

In Telecomm, there is a possible disclosure of registered self managed phone accounts due to a missing permission check.

3.3
CVE-2022-20310

In Telecomm, there is a possible disclosure of registered self managed phone accounts due to a missing permission check.

3.3
CVE-2022-20309

In PackageInstaller, there is a possible way to determine whether an app is installed, without query permissions, due to

7.5
CVE-2022-20308

In hostapd, there is a possible insecure configuration due to an insecure default value. This could lead to remote denia

3.3
CVE-2022-20307

In AlarmManagerService, there is a possible way to determine whether an app is installed, without query permissions, due

6.7
CVE-2022-20306

In Camera Provider HAL, there is a possible memory corruption due to a use after free. This could lead to local escalati

3.3
CVE-2022-20305

In ContentService, there is a possible disclosure of available account types due to a missing permission check. This cou

5.5
CVE-2022-20304

In Content, there is a possible way to determinate the user's account due to side channel information disclosure. This c

5.5
CVE-2022-20303

In ContentService, there is a possible way to determine if an account is on the device without GET_ACCOUNTS permission d

7.6
CVE-2022-20302

In Settings, there is a possible way to bypass factory reset protections due to a sandbox escape. This could lead to loc

5.5
CVE-2022-20301

In Content, there is a possible way to check if an account exists on the device due to a missing permission check. This

5.5
CVE-2022-20300

In Content, there is a possible way to check if the given account exists on the device due to a missing permission check

5.5
CVE-2022-20299

In ContentService, there is a possible way to check if the given account exists on the device due to a missing permissio

5.5
CVE-2022-20298

In ContentService, there is a possible way to check if an account exists on the device due to a missing permission check

7.8
CVE-2022-20297

In Settings, there is a possible way to bypass factory reset protections due to a logic error in the code. This could le

5.5
CVE-2022-20296

In ContentService, there is a possible way to check if an account exists on the device due to a missing permission check

5.5
CVE-2022-20295

In ContentService, there is a possible way to check if an account exists on the device due to a missing permission check

5.5
CVE-2022-20294

In Content, there is a possible way to learn about an account present on the device due to a missing permission check. T

5.5
CVE-2022-20293

In LauncherApps, there is a possible way to determine whether an app is installed, without query permissions, due to sid

7.8
CVE-2022-20292

In Settings, there is a possible way to bypass factory reset protections due to a logic error in the code. This could le

5.5
CVE-2022-20291

In AppOpsService, there is a possible way to determine whether an app is installed, without query permissions, due to si

5.5
CVE-2022-20290

In Midi, there is a possible way to learn about private midi devices due to a permissions bypass. This could lead to loc

5.5
CVE-2022-20289

In PackageInstaller, there is a possible way to determine whether an app is installed, without query permissions, due to

5.5
CVE-2022-20288

In AppSearchManagerService, there is a possible way to determine whether an app is installed, without query permissions,

5.5
CVE-2022-20287

In AppSearchManagerService, there is a possible way to determine whether an app is installed, without query permissions,

7.8
CVE-2022-20286

In Connectivity, there is a possible bypass the restriction of starting activity from background due to a logic error in

5.5
CVE-2022-20285

In PackageManager, there is a possible way to determine whether an app is installed, without query permissions, due to s

5.5
CVE-2022-20284

In Telephony, there is a possible information disclosure due to a missing permission check. This could lead to local inf

8.8
CVE-2022-20283

In Bluetooth, there is a possible out of bounds write due to an integer overflow. This could lead to remote code executi

Test your stack for 2022issues

CyberStrike tests your own apps and APIs, then verifies each finding before you see it.