What is the severity of CVE-2017-0607?

CVE-2017-0607 is rated as High severity due to its potential for elevation of privilege via a compromised privileged process.

How do I fix CVE-2017-0607?

To fix CVE-2017-0607, update your Android device to the latest security patch that addresses this vulnerability.

What software versions are affected by CVE-2017-0607?

CVE-2017-0607 affects Android devices running Linux Kernel version 3.18.

Can CVE-2017-0607 be exploited remotely?

CVE-2017-0607 cannot be exploited remotely; an attacker must first compromise a privileged process on the device.

What kind of attacks can CVE-2017-0607 facilitate?

CVE-2017-0607 can facilitate arbitrary code execution within the kernel context, potentially leading to system compromise.

Vulnerability/
CVE-2017-0607

high

7.6

CWE

704

1/5/2017

12/5/2017

26/8/2024

CVE-2017-0607: Incorrect Type Cast

First published: Mon May 01 2017(Updated: )

An elevation of privilege vulnerability in the Qualcomm sound driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as High because it first requires compromising a privileged process. Product: Android. Versions: Kernel-3.18. Android ID: A-35400551. References: QC-CR#1085928.

Credit: security@android.com

Affected Software	Affected Version	How to fix
Linux Kernel	=3.18
Android

Remedy

https://source.android.com/security/bulletin/2017-05-01

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-0607?
CVE-2017-0607 is rated as High severity due to its potential for elevation of privilege via a compromised privileged process.
How do I fix CVE-2017-0607?
To fix CVE-2017-0607, update your Android device to the latest security patch that addresses this vulnerability.
What software versions are affected by CVE-2017-0607?
CVE-2017-0607 affects Android devices running Linux Kernel version 3.18.
Can CVE-2017-0607 be exploited remotely?
CVE-2017-0607 cannot be exploited remotely; an attacker must first compromise a privileged process on the device.
What kind of attacks can CVE-2017-0607 facilitate?
CVE-2017-0607 can facilitate arbitrary code execution within the kernel context, potentially leading to system compromise.

agent/references
agent/type
agent/first-publish-date
agent/weakness
agent/severity
agent/remedy
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/event
agent/last-modified-date
agent/source
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/android-source
source/Android
agent/software-canonical-lookup
vendor/linux
canonical/linux kernel
version/linux kernel/3.18
vendor/google
canonical/android

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-0607?
CVE-2017-0607 is rated as High severity due to its potential for elevation of privilege via a compromised privileged process.
How do I fix CVE-2017-0607?
To fix CVE-2017-0607, update your Android device to the latest security patch that addresses this vulnerability.
What software versions are affected by CVE-2017-0607?
CVE-2017-0607 affects Android devices running Linux Kernel version 3.18.
Can CVE-2017-0607 be exploited remotely?
CVE-2017-0607 cannot be exploited remotely; an attacker must first compromise a privileged process on the device.
What kind of attacks can CVE-2017-0607 facilitate?
CVE-2017-0607 can facilitate arbitrary code execution within the kernel context, potentially leading to system compromise.