What is the severity of CVE-2022-20330?

CVE-2022-20330 is classified with a high severity level due to its potential for local escalation of privileges.

How do I fix CVE-2022-20330?

To fix CVE-2022-20330, users should update their Android devices to the latest available security patch provided by Google.

Who is affected by CVE-2022-20330?

CVE-2022-20330 affects devices running Android 13.0 that have not implemented the necessary security updates.

What type of vulnerability is CVE-2022-20330?

CVE-2022-20330 is a permission check vulnerability in Bluetooth that could allow unauthorized device connections.

Is user interaction needed to exploit CVE-2022-20330?

No, user interaction is not required for the exploitation of CVE-2022-20330.

Vulnerability/
CVE-2022-20330

low

3.5

CWE

862

11/8/2022

3/8/2024

CVE-2022-20330

First published: Thu Aug 11 2022(Updated: )

In Bluetooth, there is a possible way to connect or disconnect bluetooth devices without user awareness due to a missing permission check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-181962588

Credit: security@android.com security@android.com

Affected Software	Affected Version	How to fix
Google Android	=13.0

Never miss a vulnerability like this again

Reference Links

https://source.android.com/security/bulletin/android-13

Frequently Asked Questions

What is the severity of CVE-2022-20330?
CVE-2022-20330 is classified with a high severity level due to its potential for local escalation of privileges.
How do I fix CVE-2022-20330?
To fix CVE-2022-20330, users should update their Android devices to the latest available security patch provided by Google.
Who is affected by CVE-2022-20330?
CVE-2022-20330 affects devices running Android 13.0 that have not implemented the necessary security updates.
What type of vulnerability is CVE-2022-20330?
CVE-2022-20330 is a permission check vulnerability in Bluetooth that could allow unauthorized device connections.
Is user interaction needed to exploit CVE-2022-20330?
No, user interaction is not required for the exploitation of CVE-2022-20330.

agent/author
agent/type
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-api
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/last-modified-date
agent/references
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/google
canonical/google android
version/google android/13.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-20330?
CVE-2022-20330 is classified with a high severity level due to its potential for local escalation of privileges.
How do I fix CVE-2022-20330?
To fix CVE-2022-20330, users should update their Android devices to the latest available security patch provided by Google.
Who is affected by CVE-2022-20330?
CVE-2022-20330 affects devices running Android 13.0 that have not implemented the necessary security updates.
What type of vulnerability is CVE-2022-20330?
CVE-2022-20330 is a permission check vulnerability in Bluetooth that could allow unauthorized device connections.
Is user interaction needed to exploit CVE-2022-20330?
No, user interaction is not required for the exploitation of CVE-2022-20330.