What is the severity of CVE-2017-18654?

CVE-2017-18654 has a critical severity rating due to the potential for unauthorized certificate registration.

Who is affected by CVE-2017-18654?

CVE-2017-18654 affects Samsung mobile devices running Android versions 6.0, 7.0, and 7.1.

How do I fix CVE-2017-18654?

To fix CVE-2017-18654, users should update their Samsung devices to the latest available security patches.

What can an attacker do with CVE-2017-18654?

An attacker exploiting CVE-2017-18654 can register a new security certificate, compromising the device's trust.

When was CVE-2017-18654 disclosed?

CVE-2017-18654 was disclosed in September 2017 as part of the Samsung security update SVE-2017-9659.

Vulnerability/
CVE-2017-18654

high

7.5

CWE

287

7/4/2020

5/8/2024

CVE-2017-18654

First published: Tue Apr 07 2020(Updated: )

An issue was discovered on Samsung mobile devices with M(6.0) and N(7.0, 7.1) software. An unauthenticated attacker can register a new security certificate. The Samsung ID is SVE-2017-9659 (September 2017).

Credit: cve@mitre.org

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

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-18654?
CVE-2017-18654 has a critical severity rating due to the potential for unauthorized certificate registration.
Who is affected by CVE-2017-18654?
CVE-2017-18654 affects Samsung mobile devices running Android versions 6.0, 7.0, and 7.1.
How do I fix CVE-2017-18654?
To fix CVE-2017-18654, users should update their Samsung devices to the latest available security patches.
What can an attacker do with CVE-2017-18654?
An attacker exploiting CVE-2017-18654 can register a new security certificate, compromising the device's trust.
When was CVE-2017-18654 disclosed?
CVE-2017-18654 was disclosed in September 2017 as part of the Samsung security update SVE-2017-9659.

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

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-18654?
CVE-2017-18654 has a critical severity rating due to the potential for unauthorized certificate registration.
Who is affected by CVE-2017-18654?
CVE-2017-18654 affects Samsung mobile devices running Android versions 6.0, 7.0, and 7.1.
How do I fix CVE-2017-18654?
To fix CVE-2017-18654, users should update their Samsung devices to the latest available security patches.
What can an attacker do with CVE-2017-18654?
An attacker exploiting CVE-2017-18654 can register a new security certificate, compromising the device's trust.
When was CVE-2017-18654 disclosed?
CVE-2017-18654 was disclosed in September 2017 as part of the Samsung security update SVE-2017-9659.