CVE-2017-18678
First published: Tue Apr 07 2020(Updated: )
An issue was discovered on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software. An attacker can crash system processes via a Serializable object because of missing exception handling. The Samsung IDs are SVE-2017-8109, SVE-2017-8110, SVE-2017-8115, SVE-2017-8118, and SVE-2017-8119 (April 2017).
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Android | =4.4 | |
| Android | =5.0 | |
| Android | =5.1 | |
| Android | =6.0 | |
| Android | =7.0 | |
| Android | =7.1.0 | |
| Android | =7.1.1 | |
| Android | =7.1.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-18678?
CVE-2017-18678 has a moderate severity rating due to its potential to crash system processes.
How do I fix CVE-2017-18678?
To fix CVE-2017-18678, update affected Samsung mobile devices to the latest available software version.
What devices are affected by CVE-2017-18678?
CVE-2017-18678 affects Samsung mobile devices running Android versions 4.4 to 7.1.2.
What causes CVE-2017-18678?
CVE-2017-18678 is caused by missing exception handling for Serializable objects.
Can CVE-2017-18678 be exploited remotely?
Yes, an attacker can exploit CVE-2017-18678 to crash system processes remotely.
- agent/softwarecombine
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/google
- canonical/android
- version/android/4.4
- version/android/5.0
- version/android/5.1
- version/android/6.0
- version/android/7.0
- version/android/7.1.0
- version/android/7.1.1
- version/android/7.1.2