What is the severity of CVE-2022-20527?

The severity of CVE-2022-20527 is classified as moderate due to the potential for local information disclosure.

How do I fix CVE-2022-20527?

To fix CVE-2022-20527, users should update their Android device to the latest version that addresses this vulnerability.

Who is affected by CVE-2022-20527?

CVE-2022-20527 affects users running Android version 13.0.

What kind of attack does CVE-2022-20527 enable?

CVE-2022-20527 enables a possible local information disclosure attack due to a missing bounds check.

Is user interaction required for exploiting CVE-2022-20527?

No, user interaction is not needed for exploiting CVE-2022-20527.

Vulnerability/
CVE-2022-20527

medium

5.5

CWE

125

16/12/2022

21/4/2025

CVE-2022-20527

First published: Fri Dec 16 2022(Updated: )

In HalCoreCallback of halcore.cc, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure from the NFC firmware with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-229994861

Credit: security@android.com

Affected Software	Affected Version	How to fix
Android	=13.0
	=13.0

Never miss a vulnerability like this again

Reference Links

https://source.android.com/security/bulletin/pixel/2022-12-01

Frequently Asked Questions

What is the severity of CVE-2022-20527?
The severity of CVE-2022-20527 is classified as moderate due to the potential for local information disclosure.
How do I fix CVE-2022-20527?
To fix CVE-2022-20527, users should update their Android device to the latest version that addresses this vulnerability.
Who is affected by CVE-2022-20527?
CVE-2022-20527 affects users running Android version 13.0.
What kind of attack does CVE-2022-20527 enable?
CVE-2022-20527 enables a possible local information disclosure attack due to a missing bounds check.
Is user interaction required for exploiting CVE-2022-20527?
No, user interaction is not needed for exploiting CVE-2022-20527.

agent/type
agent/severity
agent/references
agent/weakness
agent/author
agent/description
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/software-canonical-lookup
agent/last-modified-date
agent/source
agent/softwarecombine
agent/tags
agent/event
vendor/google
canonical/android
version/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-20527?
The severity of CVE-2022-20527 is classified as moderate due to the potential for local information disclosure.
How do I fix CVE-2022-20527?
To fix CVE-2022-20527, users should update their Android device to the latest version that addresses this vulnerability.
Who is affected by CVE-2022-20527?
CVE-2022-20527 affects users running Android version 13.0.
What kind of attack does CVE-2022-20527 enable?
CVE-2022-20527 enables a possible local information disclosure attack due to a missing bounds check.
Is user interaction required for exploiting CVE-2022-20527?
No, user interaction is not needed for exploiting CVE-2022-20527.