Vulmon
Recent Vulnerabilities
Product List
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-18671
An issue exists on Samsung mobile devices with L(5.0/5.1), M(6.0), and N(7.x) software. Intents related to Wi-Fi have incorrect exception handling, leading to a crash of system processes. The Samsung ID is SVE-2017-8389 (May 2017).
Google Android 7.1.0
Google Android 7.1.2
Google Android 6.0
Google Android 7.0
Google Android 5.0
Google Android 7.1.1
Google Android 5.1
4.9
CVSSv2
CVE-2017-18672
An issue exists on Samsung mobile devices with L(5.0/5.1), M(6.0), and N(7.x) software. Because of incorrect exception handling for Intents, a local attacker can force a reboot within framework.jar. The Samsung ID is SVE-2017-8390 (May 2017).
Google Android 7.1.0
Google Android 7.1.2
Google Android 6.0
Google Android 7.0
Google Android 5.0
Google Android 7.1.1
Google Android 5.1
5
CVSSv2
CVE-2017-18675
An issue exists on Samsung mobile devices with M(6.0) and N(7.x) (Exynos7420 or Exynox8890 chipsets) software. The Camera application can leak uninitialized memory via ion. The Samsung ID is SVE-2016-6989 (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
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 6.0
Google Android 5.0
Google Android 5.1
7.8
CVSSv2
CVE-2017-18685
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), and M(6.0) software. The InputMethod application can cause a system crash via a malformed serializable object in an Intent. The Samsung ID is SVE-2016-7123 (February 2017).
Google Android 6.0
Google Android 5.0
Google Android 4.4
Google Android 5.1
5
CVSSv2
CVE-2017-18687
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.0) software. An attacker can obtain the full pathnames of sdcard files by reading the system protected log upon reception of a certain intent. The Samsung ID is SVE-2016-7183 (January 2017).
Google Android 6.0
Google Android 7.0
Google Android 5.0
Google Android 4.4
Google Android 5.1
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
6.8
CVSSv2
CVE-2017-18647
An issue exists on Samsung mobile devices with M(6,x) and N(7.0) software. The TA Scrypto v1.0 implementation in Secure Driver has a race condition with a resultant buffer overflow. The Samsung IDs are SVE-2017-8973, SVE-2017-8974, and SVE-2017-8975 (November 2017).
Google Android 6.0.1
Google Android 6.0
Google Android 7.0
7.5
CVSSv2
CVE-2017-18652
An issue exists on Samsung mobile devices with M(6.0) and N(7.x) software. SVoice allows arbitrary code execution by changing dynamic libraries. The Samsung ID is SVE-2017-9299 (September 2017).
Google Android 7.1.0
Google Android 7.1.2
Google Android 6.0
Google Android 7.0
Google Android 7.1.1
5
CVSSv2
CVE-2017-18654
An issue exists 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).
Google Android 6.0
Google Android 7.0
Google Android 7.1
CVSSv2
CVSSv2
CVSSv3
VMScore
Recommendations:
CVE-2024-37316
firmware
CVE-2024-30078
CVE-2024-5995
remote code execution
logic flaw
CVE-2024-20693
CVE-2024-37315
CVE-2024-5464
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
NEXT »