Vulmon
Recent Vulnerabilities
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
google android 6.0 vulnerabilities and exploits
(subscribe to this query)
5
CVSSv2
CVE-2017-18677
An issue exists on Samsung mobile devices with M(6.0) and N(7.x) software. Because of an unprotected Intent, an attacker can reset the configuration of certain applications. The Samsung ID is SVE-2016-7142 (April 2017).
Google Android 6.0
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
5
CVSSv2
CVE-2017-18678
An issue exists 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,...
Google Android 4.4
Google Android 5.0
Google Android 5.1
Google Android 6.0
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
7.8
CVSSv2
CVE-2017-18679
An issue exists on Samsung mobile devices with M(6.0) software. SLocation can cause a system crash via a call to an API that is not implemented. The Samsung ID is SVE-2017-8285 (April 2017).
Google Android 6.0
3.6
CVSSv2
CVE-2017-18680
An issue exists on Samsung mobile devices with L(5.0/5.1) and M(6.0) (tablets) software. The lockscreen interface allows Add User actions, leading to an unintended ability to access user data in external storage. The Samsung ID is SVE-2016-7797 (March 2017).
Google Android 5.0
Google Android 5.1
Google Android 6.0
7.5
CVSSv2
CVE-2017-18683
An issue exists on Samsung mobile devices with L(5.0/5.1) and M(6.0) software. SVoice allows Hare Hunting during application installation. The Samsung ID is SVE-2016-6942 (February 2017).
Google Android 5.0
Google Android 5.1
Google Android 6.0
7.5
CVSSv2
CVE-2017-18684
An issue exists on Samsung mobile devices with L(5.0/5.1) and M(6.0) software. SVoice allows provider seizure via an application that uses a custom provider. The Samsung ID is SVE-2016-6942 (February 2017).
Google Android 5.0
Google Android 5.1
Google Android 6.0
5
CVSSv2
CVE-2017-18686
An issue exists on Samsung mobile devices with M(6.0) and N(7.0) software. Contact information can leak to a log file because of the broadcasting of an unprotected intent. The Samsung ID is SVE-2016-7180 (February 2017).
Google Android 6.0
Google Android 7.0
5
CVSSv2
CVE-2017-18688
An issue exists 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).
Google Android 5.1
Google Android 6.0
Google Android 7.0
4.3
CVSSv2
CVE-2017-18689
An issue exists on Samsung mobile devices with M(6.0) and N(7.0) (Exynos5433, Exynos7420, or Exynos7870 chipsets) software. An attacker can bypass a ko (aka Kernel Module) signature by modifying the count of kernel modules. The Samsung ID is SVE-2016-7466 (January 2017).
Google Android 6.0
Google Android 7.0
7.5
CVSSv2
CVE-2017-18690
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.0) (Exynos54xx, Exynos7420, Exynos8890, or Exynos8895 chipsets) software. There is a buffer overflow in the sensor hub. The Samsung ID is SVE-2016-7484 (January 2017).
Google Android 4.4
Google Android 5.0
Google Android 5.1
Google Android 6.0
Google Android 7.0
CVSSv2
CVSSv2
CVSSv3
VMScore
Recommendations:
privilege escalation
CVE-2024-20696
CVE-2024-29829
CVE-2024-33999
CVE-2024-35646
physical
CVE-2024-24919
CVE-2024-31030
local users
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
« PREV
1
2
3
4
5
6
7
8
9
10
NEXT »