What is the severity of CVE-2017-18663?

CVE-2017-18663 has a medium severity due to its potential to crash system processes.

How do I fix CVE-2017-18663?

To fix CVE-2017-18663, ensure your Samsung mobile device is updated to the latest software version.

Which devices are affected by CVE-2017-18663?

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

What causes the CVE-2017-18663 vulnerability?

CVE-2017-18663 is caused by missing Intent exception handling in the system_server process.

When was CVE-2017-18663 discovered?

CVE-2017-18663 was discovered in July 2017.

Vulnerability/
CVE-2017-18663

high

7.5

CWE

755

7/4/2020

5/8/2024

CVE-2017-18663

First published: Tue Apr 07 2020(Updated: )

An issue was discovered on Samsung mobile devices with N(7.x) software. Because of missing Intent exception handling, system_server can have a NullPointerException with a crash of a system process. The Samsung IDs are SVE-2017-9122, SVE-2017-9123, SVE-2017-9124, and SVE-2017-9126 (July 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-18663?
CVE-2017-18663 has a medium severity due to its potential to crash system processes.
How do I fix CVE-2017-18663?
To fix CVE-2017-18663, ensure your Samsung mobile device is updated to the latest software version.
Which devices are affected by CVE-2017-18663?
CVE-2017-18663 affects Samsung mobile devices running Android 7.0 to 7.1.2.
What causes the CVE-2017-18663 vulnerability?
CVE-2017-18663 is caused by missing Intent exception handling in the system_server process.
When was CVE-2017-18663 discovered?
CVE-2017-18663 was discovered in July 2017.

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/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-18663?
CVE-2017-18663 has a medium severity due to its potential to crash system processes.
How do I fix CVE-2017-18663?
To fix CVE-2017-18663, ensure your Samsung mobile device is updated to the latest software version.
Which devices are affected by CVE-2017-18663?
CVE-2017-18663 affects Samsung mobile devices running Android 7.0 to 7.1.2.
What causes the CVE-2017-18663 vulnerability?
CVE-2017-18663 is caused by missing Intent exception handling in the system_server process.
When was CVE-2017-18663 discovered?
CVE-2017-18663 was discovered in July 2017.