What is the severity of CVE-2017-18673?

CVE-2017-18673 is considered a high severity vulnerability due to its impact on the security of a user's ability to track their device.

How do I fix CVE-2017-18673?

To fix CVE-2017-18673, users should update their Samsung mobile devices to the latest available firmware provided by Samsung.

What are the implications of CVE-2017-18673?

The implications of CVE-2017-18673 include the potential inability for device owners to locate or disable their device after it has been stolen.

Which devices are affected by CVE-2017-18673?

CVE-2017-18673 affects Samsung mobile devices running Android versions 7.0 to 7.1.2.

Is there a workaround for CVE-2017-18673?

There are no official workarounds for CVE-2017-18673 other than applying the software update as soon as it is available.

Vulnerability/
CVE-2017-18673

low

2.4

CWE

7/4/2020

5/8/2024

CVE-2017-18673: Input Validation

First published: Tue Apr 07 2020(Updated: )

An issue was discovered on Samsung mobile devices with N(7.x) software. An attacker can disable the Location service on a locked device, making it impossible for the rightful owner to find a stolen device. The Samsung ID is SVE-2017-8524 (May 2017).

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
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-18673?
CVE-2017-18673 is considered a high severity vulnerability due to its impact on the security of a user's ability to track their device.
How do I fix CVE-2017-18673?
To fix CVE-2017-18673, users should update their Samsung mobile devices to the latest available firmware provided by Samsung.
What are the implications of CVE-2017-18673?
The implications of CVE-2017-18673 include the potential inability for device owners to locate or disable their device after it has been stolen.
Which devices are affected by CVE-2017-18673?
CVE-2017-18673 affects Samsung mobile devices running Android versions 7.0 to 7.1.2.
Is there a workaround for CVE-2017-18673?
There are no official workarounds for CVE-2017-18673 other than applying the software update as soon as it is available.

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/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-18673?
CVE-2017-18673 is considered a high severity vulnerability due to its impact on the security of a user's ability to track their device.
How do I fix CVE-2017-18673?
To fix CVE-2017-18673, users should update their Samsung mobile devices to the latest available firmware provided by Samsung.
What are the implications of CVE-2017-18673?
The implications of CVE-2017-18673 include the potential inability for device owners to locate or disable their device after it has been stolen.
Which devices are affected by CVE-2017-18673?
CVE-2017-18673 affects Samsung mobile devices running Android versions 7.0 to 7.1.2.
Is there a workaround for CVE-2017-18673?
There are no official workarounds for CVE-2017-18673 other than applying the software update as soon as it is available.