What is the severity of CVE-2017-13311?

CVE-2017-13311 is considered a high severity vulnerability due to its potential for local privilege escalation.

How do I fix CVE-2017-13311?

To fix CVE-2017-13311, update your Android device to the latest version that addresses this security issue.

Which versions of Android are affected by CVE-2017-13311?

CVE-2017-13311 affects Android versions 7.0, 7.1.1, 7.1.2, 8.0, and 8.1.

What type of vulnerability is CVE-2017-13311?

CVE-2017-13311 is a permissions bypass vulnerability that can lead to local escalation of privilege.

Is user interaction required to exploit CVE-2017-13311?

No, user interaction is not required to exploit CVE-2017-13311.

Vulnerability/
CVE-2017-13311

high

7.8

CWE

276

7/5/2018

15/11/2024

18/12/2024

CVE-2017-13311

First published: Mon May 07 2018(Updated: )

In the read() function of ProcessStats.java, there is a possible read/write serialization issue leading to a permissions bypass. This could lead to local escalation of privilege where an app can start an activity with system privileges with no additional execution privileges needed. User interaction is not needed for exploitation.

Credit: security@android.com

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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-13311?
CVE-2017-13311 is considered a high severity vulnerability due to its potential for local privilege escalation.
How do I fix CVE-2017-13311?
To fix CVE-2017-13311, update your Android device to the latest version that addresses this security issue.
Which versions of Android are affected by CVE-2017-13311?
CVE-2017-13311 affects Android versions 7.0, 7.1.1, 7.1.2, 8.0, and 8.1.
What type of vulnerability is CVE-2017-13311?
CVE-2017-13311 is a permissions bypass vulnerability that can lead to local escalation of privilege.
Is user interaction required to exploit CVE-2017-13311?
No, user interaction is not required to exploit CVE-2017-13311.

agent/type
agent/first-publish-date
collector/android-source
source/Android
agent/software-canonical-lookup
agent/references
agent/description
agent/author
agent/weakness
agent/event
collector/mitre-cve
source/MITRE
collector/nvd-api
source/NVD
agent/severity
agent/last-modified-date
agent/tags
agent/softwarecombine
agent/source
vendor/google
canonical/google android
version/google android/7.0
version/google android/7.1.1
version/google android/7.1.2
version/google android/8.0
version/google android/8.1

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-2017-13311?
CVE-2017-13311 is considered a high severity vulnerability due to its potential for local privilege escalation.
How do I fix CVE-2017-13311?
To fix CVE-2017-13311, update your Android device to the latest version that addresses this security issue.
Which versions of Android are affected by CVE-2017-13311?
CVE-2017-13311 affects Android versions 7.0, 7.1.1, 7.1.2, 8.0, and 8.1.
What type of vulnerability is CVE-2017-13311?
CVE-2017-13311 is a permissions bypass vulnerability that can lead to local escalation of privilege.
Is user interaction required to exploit CVE-2017-13311?
No, user interaction is not required to exploit CVE-2017-13311.