What is the severity of CVE-2019-1993?

CVE-2019-1993 is classified as a high severity vulnerability due to the potential for local escalation of privilege.

How do I fix CVE-2019-1993?

To fix CVE-2019-1993, ensure that your Android device is updated to the latest security patch provided by the manufacturer.

What causes CVE-2019-1993?

CVE-2019-1993 is caused by a memory corruption issue resulting from an integer overflow in the register_app function.

Who is affected by CVE-2019-1993?

CVE-2019-1993 affects users on Android versions 8.0, 8.1, and 9.0.

Is user interaction required for exploiting CVE-2019-1993?

No, user interaction is not needed for exploitation of CVE-2019-1993.

Vulnerability/
CVE-2019-1993

high

7.8

CWE

190 787

4/2/2019

28/2/2019

21/11/2024

CVE-2019-1993: Integer Overflow

First published: Mon Feb 04 2019(Updated: )

In register_app of btif_hd.cc, there is a possible memory corruption due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android-8.0 Android-8.1 Android-9. Android ID: A-119819889.

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

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-1993?
CVE-2019-1993 is classified as a high severity vulnerability due to the potential for local escalation of privilege.
How do I fix CVE-2019-1993?
To fix CVE-2019-1993, ensure that your Android device is updated to the latest security patch provided by the manufacturer.
What causes CVE-2019-1993?
CVE-2019-1993 is caused by a memory corruption issue resulting from an integer overflow in the register_app function.
Who is affected by CVE-2019-1993?
CVE-2019-1993 affects users on Android versions 8.0, 8.1, and 9.0.
Is user interaction required for exploiting CVE-2019-1993?
No, user interaction is not needed for exploitation of CVE-2019-1993.

agent/references
agent/type
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/weakness
agent/severity
agent/description
collector/android-source
source/Android
agent/software-canonical-lookup
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/last-modified-date
agent/author
agent/softwarecombine
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

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-2019-1993?
CVE-2019-1993 is classified as a high severity vulnerability due to the potential for local escalation of privilege.
How do I fix CVE-2019-1993?
To fix CVE-2019-1993, ensure that your Android device is updated to the latest security patch provided by the manufacturer.
What causes CVE-2019-1993?
CVE-2019-1993 is caused by a memory corruption issue resulting from an integer overflow in the register_app function.
Who is affected by CVE-2019-1993?
CVE-2019-1993 affects users on Android versions 8.0, 8.1, and 9.0.
Is user interaction required for exploiting CVE-2019-1993?
No, user interaction is not needed for exploitation of CVE-2019-1993.