What is the severity of CVE-2018-9549?

CVE-2018-9549 has a critical severity rating due to its potential for remote code execution.

What versions of Android are affected by CVE-2018-9549?

CVE-2018-9549 affects Android versions 7.0, 7.1.1, 7.1.2, 8.0, 8.1, and 9.0.

How does CVE-2018-9549 allow an attacker to exploit devices?

CVE-2018-9549 allows an attacker to exploit devices through an out of bounds write that requires user interaction.

How do I fix CVE-2018-9549?

The recommended fix for CVE-2018-9549 is to update your Android device to the latest security patch provided by Google.

Is user interaction required for exploiting CVE-2018-9549?

Yes, user interaction is necessary for exploiting CVE-2018-9549.

Vulnerability/
CVE-2018-9549

critical

9.3

CWE

787

3/12/2018

6/12/2018

26/8/2024

CVE-2018-9549

First published: Mon Dec 03 2018(Updated: )

In lppTransposer of lpp_tran.cpp there is a possible out of bounds write due to missing bounds check. This could lead to remote code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android. Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9. Android ID: A-112160868.

Credit: security@android.com

Affected Software	Affected Version	How to fix
Android
Android	=7.0
Android	=7.1.1
Android	=7.1.2
Android	=8.0
Android	=8.1
Android	=9.0

Remedy

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-9549?
CVE-2018-9549 has a critical severity rating due to its potential for remote code execution.
What versions of Android are affected by CVE-2018-9549?
CVE-2018-9549 affects Android versions 7.0, 7.1.1, 7.1.2, 8.0, 8.1, and 9.0.
How does CVE-2018-9549 allow an attacker to exploit devices?
CVE-2018-9549 allows an attacker to exploit devices through an out of bounds write that requires user interaction.
How do I fix CVE-2018-9549?
The recommended fix for CVE-2018-9549 is to update your Android device to the latest security patch provided by Google.
Is user interaction required for exploiting CVE-2018-9549?
Yes, user interaction is necessary for exploiting CVE-2018-9549.

agent/references
agent/type
agent/first-publish-date
agent/severity
agent/weakness
agent/author
agent/remedy
agent/description
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/event
agent/last-modified-date
agent/source
agent/tags
collector/android-source
source/Android
agent/software-canonical-lookup
agent/software-canonical-lookup-request
collector/nvd-index
vendor/google
canonical/android
version/android/7.0
version/android/7.1.1
version/android/7.1.2
version/android/8.0
version/android/8.1
version/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-2018-9549?
CVE-2018-9549 has a critical severity rating due to its potential for remote code execution.
What versions of Android are affected by CVE-2018-9549?
CVE-2018-9549 affects Android versions 7.0, 7.1.1, 7.1.2, 8.0, 8.1, and 9.0.
How does CVE-2018-9549 allow an attacker to exploit devices?
CVE-2018-9549 allows an attacker to exploit devices through an out of bounds write that requires user interaction.
How do I fix CVE-2018-9549?
The recommended fix for CVE-2018-9549 is to update your Android device to the latest security patch provided by Google.
Is user interaction required for exploiting CVE-2018-9549?
Yes, user interaction is necessary for exploiting CVE-2018-9549.