What is the severity of CVE-2017-18660?

CVE-2017-18660 has a medium severity rating due to its potential for causing device instability through buffer overflow.

How do I fix CVE-2017-18660?

To fix CVE-2017-18660, update Samsung mobile devices to the latest firmware version provided by Samsung.

Which devices are affected by CVE-2017-18660?

CVE-2017-18660 affects specific Samsung mobile devices running Android 6.0 (Marshmallow) and versions 7.0 through 7.1.2 (Nougat).

What is the impact of CVE-2017-18660?

The impact of CVE-2017-18660 can include potential remote code execution or unauthorized access resulting from the buffer overflow.

When was CVE-2017-18660 disclosed?

CVE-2017-18660 was disclosed in July 2017 as part of the Samsung security updates.

Vulnerability/
CVE-2017-18660

critical

9.8

CWE

120 119

7/4/2020

5/8/2024

CVE-2017-18660: Buffer Overflow

First published: Tue Apr 07 2020(Updated: )

An issue was discovered on Samsung mobile devices with M(6.0) and N(7.x) software. There is a buffer overflow in tlc_server. The Samsung ID is SVE-2017-8888 (July 2017).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=6.0
Google Android	=7.0
Google Android	=7.1.0
Google Android	=7.1.1
Google Android	=7.1.2

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-18660?
CVE-2017-18660 has a medium severity rating due to its potential for causing device instability through buffer overflow.
How do I fix CVE-2017-18660?
To fix CVE-2017-18660, update Samsung mobile devices to the latest firmware version provided by Samsung.
Which devices are affected by CVE-2017-18660?
CVE-2017-18660 affects specific Samsung mobile devices running Android 6.0 (Marshmallow) and versions 7.0 through 7.1.2 (Nougat).
What is the impact of CVE-2017-18660?
The impact of CVE-2017-18660 can include potential remote code execution or unauthorized access resulting from the buffer overflow.
When was CVE-2017-18660 disclosed?
CVE-2017-18660 was disclosed in July 2017 as part of the Samsung security updates.

agent/type
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/weakness
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/7.0
version/google android/7.1.0
version/google android/7.1.1
version/google android/7.1.2

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-18660?
CVE-2017-18660 has a medium severity rating due to its potential for causing device instability through buffer overflow.
How do I fix CVE-2017-18660?
To fix CVE-2017-18660, update Samsung mobile devices to the latest firmware version provided by Samsung.
Which devices are affected by CVE-2017-18660?
CVE-2017-18660 affects specific Samsung mobile devices running Android 6.0 (Marshmallow) and versions 7.0 through 7.1.2 (Nougat).
What is the impact of CVE-2017-18660?
The impact of CVE-2017-18660 can include potential remote code execution or unauthorized access resulting from the buffer overflow.
When was CVE-2017-18660 disclosed?
CVE-2017-18660 was disclosed in July 2017 as part of the Samsung security updates.