What is the severity of CVE-2020-0117?

CVE-2020-0117 is rated as a critical vulnerability due to its potential for remote code execution.

How do I fix CVE-2020-0117?

To fix CVE-2020-0117, update your Android device to the latest security patch provided by Google.

Which Android versions are affected by CVE-2020-0117?

CVE-2020-0117 affects Android versions 8.0, 8.1, 9.0, and 10.0.

What could happen if CVE-2020-0117 is exploited?

If exploited, CVE-2020-0117 can lead to remote code execution within the Bluetooth server without requiring user interaction.

Who is vulnerable to CVE-2020-0117?

Users with Android devices running versions 8.0 to 10.0 are vulnerable to CVE-2020-0117.

Vulnerability/
CVE-2020-0117

critical

CWE

190 787

1/6/2020

10/6/2020

4/8/2024

CVE-2020-0117: Integer Overflow

First published: Mon Jun 01 2020(Updated: )

In aes_cmac of aes_cmac.cc, there is a possible out of bounds write due to an integer overflow. This could lead to remote code execution in the bluetooth server with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.1 Android-9 Android-10 Android-8.0Android ID: A-151155194

Credit: security@android.com

Affected Software	Affected Version	How to fix
Google Android	=8.0
Google Android	=8.1
Google Android	=9.0
Google Android	=10.0

Remedy

https://source.android.com/security/bulletin/2020-06-01

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-0117?
CVE-2020-0117 is rated as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2020-0117?
To fix CVE-2020-0117, update your Android device to the latest security patch provided by Google.
Which Android versions are affected by CVE-2020-0117?
CVE-2020-0117 affects Android versions 8.0, 8.1, 9.0, and 10.0.
What could happen if CVE-2020-0117 is exploited?
If exploited, CVE-2020-0117 can lead to remote code execution within the Bluetooth server without requiring user interaction.
Who is vulnerable to CVE-2020-0117?
Users with Android devices running versions 8.0 to 10.0 are vulnerable to CVE-2020-0117.

agent/type
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/references
agent/remedy
agent/weakness
agent/author
agent/severity
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/softwarecombine
collector/android-source
source/Android
agent/software-canonical-lookup
agent/tags
agent/event
agent/source
vendor/google
canonical/google android
version/google android/8.0
version/google android/8.1
version/google android/9.0
version/google android/10.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-2020-0117?
CVE-2020-0117 is rated as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2020-0117?
To fix CVE-2020-0117, update your Android device to the latest security patch provided by Google.
Which Android versions are affected by CVE-2020-0117?
CVE-2020-0117 affects Android versions 8.0, 8.1, 9.0, and 10.0.
What could happen if CVE-2020-0117 is exploited?
If exploited, CVE-2020-0117 can lead to remote code execution within the Bluetooth server without requiring user interaction.
Who is vulnerable to CVE-2020-0117?
Users with Android devices running versions 8.0 to 10.0 are vulnerable to CVE-2020-0117.