What is the severity of CVE-2015-9179?

CVE-2015-9179 is classified as a high severity vulnerability due to potential buffer overflow risks.

How do I fix CVE-2015-9179?

To fix CVE-2015-9179, ensure that your Android device is updated to the security patch level of April 2018 or later.

Which systems are affected by CVE-2015-9179?

CVE-2015-9179 affects Android devices prior to the April 2018 security patch level that utilize Qualcomm Snapdragon Mobile MSM8974.

What type of vulnerability is CVE-2015-9179?

CVE-2015-9179 is a buffer overflow vulnerability caused by a lack of length checking in the OEMCrypto_DeriveKeysFromSessionKey() function.

What causes the buffer overflow in CVE-2015-9179?

The buffer overflow in CVE-2015-9179 is caused by improper length checking when deriving keys from a session key.

Vulnerability/
CVE-2015-9179

critical

CWE

119

2/4/2018

18/4/2018

16/9/2024

CVE-2015-9179: Buffer Overflow

First published: Mon Apr 02 2018(Updated: )

In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile MSM8974, lack of length checking in OEMCrypto_DeriveKeysFromSessionKey() could lead to a buffer overflow vulnerability.

Credit: product-security@qualcomm.com

Affected Software	Affected Version	How to fix
Google Android
Qualcomm Msm8974 Firmware
Qualcomm Msm8974

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2015-9179?
CVE-2015-9179 is classified as a high severity vulnerability due to potential buffer overflow risks.
How do I fix CVE-2015-9179?
To fix CVE-2015-9179, ensure that your Android device is updated to the security patch level of April 2018 or later.
Which systems are affected by CVE-2015-9179?
CVE-2015-9179 affects Android devices prior to the April 2018 security patch level that utilize Qualcomm Snapdragon Mobile MSM8974.
What type of vulnerability is CVE-2015-9179?
CVE-2015-9179 is a buffer overflow vulnerability caused by a lack of length checking in the OEMCrypto_DeriveKeysFromSessionKey() function.
What causes the buffer overflow in CVE-2015-9179?
The buffer overflow in CVE-2015-9179 is caused by improper length checking when deriving keys from a session key.

agent/references
agent/type
agent/first-publish-date
agent/author
agent/severity
agent/weakness
agent/description
collector/nvd-index
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/android-source
source/Android
agent/software-canonical-lookup
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/source
vendor/qualcomm
canonical/qualcomm msm8974 firmware
canonical/qualcomm msm8974
vendor/google
canonical/google 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-2015-9179?
CVE-2015-9179 is classified as a high severity vulnerability due to potential buffer overflow risks.
How do I fix CVE-2015-9179?
To fix CVE-2015-9179, ensure that your Android device is updated to the security patch level of April 2018 or later.
Which systems are affected by CVE-2015-9179?
CVE-2015-9179 affects Android devices prior to the April 2018 security patch level that utilize Qualcomm Snapdragon Mobile MSM8974.
What type of vulnerability is CVE-2015-9179?
CVE-2015-9179 is a buffer overflow vulnerability caused by a lack of length checking in the OEMCrypto_DeriveKeysFromSessionKey() function.
What causes the buffer overflow in CVE-2015-9179?
The buffer overflow in CVE-2015-9179 is caused by improper length checking when deriving keys from a session key.