What is the severity of CVE-2017-18688?

CVE-2017-18688 has a moderate severity level due to potential information disclosure vulnerabilities.

How do I fix CVE-2017-18688?

To mitigate CVE-2017-18688, it is recommended to update your Samsung mobile device to the latest software version.

Which devices are affected by CVE-2017-18688?

CVE-2017-18688 affects Samsung mobile devices running Android 5.1, 6.0, and 7.0.

What type of vulnerability is CVE-2017-18688?

CVE-2017-18688 is classified as an information disclosure vulnerability affecting memory locations.

When was CVE-2017-18688 reported?

CVE-2017-18688 was reported in January 2017, alongside the Samsung ID SVE-2016-7340.

Vulnerability/
CVE-2017-18688

high

7.5

CWE

125

7/4/2020

5/8/2024

CVE-2017-18688

First published: Tue Apr 07 2020(Updated: )

An issue was discovered on Samsung mobile devices with L(5.1), M(6.0), and N(7.0) software. There is an information disclosure (of memory locations outside a buffer) via /dev/dsm_ctrl_dev. The Samsung ID is SVE-2016-7340 (January 2017).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Google Android	=5.1
Google Android	=6.0
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-18688?
CVE-2017-18688 has a moderate severity level due to potential information disclosure vulnerabilities.
How do I fix CVE-2017-18688?
To mitigate CVE-2017-18688, it is recommended to update your Samsung mobile device to the latest software version.
Which devices are affected by CVE-2017-18688?
CVE-2017-18688 affects Samsung mobile devices running Android 5.1, 6.0, and 7.0.
What type of vulnerability is CVE-2017-18688?
CVE-2017-18688 is classified as an information disclosure vulnerability affecting memory locations.
When was CVE-2017-18688 reported?
CVE-2017-18688 was reported in January 2017, alongside the Samsung ID SVE-2016-7340.

agent/type
agent/softwarecombine
collector/nvd-index
agent/software-canonical-lookup-request
collector/mitre-cve
source/MITRE
agent/severity
agent/references
agent/last-modified-date
agent/weakness
agent/author
agent/tags
agent/first-publish-date
agent/description
agent/event
agent/source
vendor/google
canonical/google android
version/google android/5.1
version/google android/6.0
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-18688?
CVE-2017-18688 has a moderate severity level due to potential information disclosure vulnerabilities.
How do I fix CVE-2017-18688?
To mitigate CVE-2017-18688, it is recommended to update your Samsung mobile device to the latest software version.
Which devices are affected by CVE-2017-18688?
CVE-2017-18688 affects Samsung mobile devices running Android 5.1, 6.0, and 7.0.
What type of vulnerability is CVE-2017-18688?
CVE-2017-18688 is classified as an information disclosure vulnerability affecting memory locations.
When was CVE-2017-18688 reported?
CVE-2017-18688 was reported in January 2017, alongside the Samsung ID SVE-2016-7340.