What is the severity of CVE-2017-18647?

CVE-2017-18647 is considered a critical vulnerability due to the potential for buffer overflow and exploitation on affected Samsung mobile devices.

How do I fix CVE-2017-18647?

To fix CVE-2017-18647, ensure that your Samsung mobile device is updated to the latest firmware version provided by Samsung.

What devices are affected by CVE-2017-18647?

CVE-2017-18647 affects Samsung mobile devices running Android versions 6.0, 6.0.1, and 7.0.

What are the consequences of exploiting CVE-2017-18647?

Exploiting CVE-2017-18647 could allow attackers to execute arbitrary code, potentially compromising the entire device.

When was CVE-2017-18647 discovered?

CVE-2017-18647 was discovered in November 2017 as part of a series of vulnerabilities reported for Samsung devices.

Vulnerability/
CVE-2017-18647

high

8.1

CWE

362 119

7/4/2020

5/8/2024

CVE-2017-18647: Race Condition

First published: Tue Apr 07 2020(Updated: )

An issue was discovered on Samsung mobile devices with M(6,x) and N(7.0) software. The TA Scrypto v1.0 implementation in Secure Driver has a race condition with a resultant buffer overflow. The Samsung IDs are SVE-2017-8973, SVE-2017-8974, and SVE-2017-8975 (November 2017).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=6.0
Google Android	=6.0.1
Google Android	=7.0

Never miss a vulnerability like this again

Reference Links

https://security.samsungmobile.com/securityUpdate.smsb

Frequently Asked Questions

What is the severity of CVE-2017-18647?
CVE-2017-18647 is considered a critical vulnerability due to the potential for buffer overflow and exploitation on affected Samsung mobile devices.
How do I fix CVE-2017-18647?
To fix CVE-2017-18647, ensure that your Samsung mobile device is updated to the latest firmware version provided by Samsung.
What devices are affected by CVE-2017-18647?
CVE-2017-18647 affects Samsung mobile devices running Android versions 6.0, 6.0.1, and 7.0.
What are the consequences of exploiting CVE-2017-18647?
Exploiting CVE-2017-18647 could allow attackers to execute arbitrary code, potentially compromising the entire device.
When was CVE-2017-18647 discovered?
CVE-2017-18647 was discovered in November 2017 as part of a series of vulnerabilities reported for Samsung devices.

agent/type
agent/weakness
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/author
agent/last-modified-date
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/google
canonical/google android
version/google android/6.0
version/google android/6.0.1
version/google android/7.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-2017-18647?
CVE-2017-18647 is considered a critical vulnerability due to the potential for buffer overflow and exploitation on affected Samsung mobile devices.
How do I fix CVE-2017-18647?
To fix CVE-2017-18647, ensure that your Samsung mobile device is updated to the latest firmware version provided by Samsung.
What devices are affected by CVE-2017-18647?
CVE-2017-18647 affects Samsung mobile devices running Android versions 6.0, 6.0.1, and 7.0.
What are the consequences of exploiting CVE-2017-18647?
Exploiting CVE-2017-18647 could allow attackers to execute arbitrary code, potentially compromising the entire device.
When was CVE-2017-18647 discovered?
CVE-2017-18647 was discovered in November 2017 as part of a series of vulnerabilities reported for Samsung devices.