Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2021-0333

CVE-2022-20223 (High) detected in Settingsandroid-10.0.0_r44

mend-bolt-for-github opened this issue · 4 comments

CVE-2022-20223 - High Severity Vulnerability

Vulnerable Library - Settingsandroid-10.0.0_r44

Library home page: https://android.googlesource.com/platform/packages/apps/Settings

Found in HEAD commit: a353664da30a0b95adee9281a4af5c1d5cacc22e

Found in base branch: master

Vulnerable Source Files (1)

/src/com/android/settings/users/AppRestrictionsFragment.java

Vulnerability Details

In assertSafeToStartCustomActivity of AppRestrictionsFragment.java, there is a possible way to start a phone call without permissions due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-223578534

Publish Date: 2022-07-13

URL: CVE-2022-20223

CVSS 3 Score Details (7.8)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Local
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: High
    • Integrity Impact: High
    • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://android.googlesource.com/platform/packages/apps/Settings/+/abadb382114fa8af5209295c9bae2ca2b08935f3

Release Date: 2022-07-13

Fix Resolution: android-12.1.0_r9


Step up your Open Source Security Game with Mend here

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.