Vulmon
Recent Vulnerabilities
Product List
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
google android 5.1 vulnerabilities and exploits
(subscribe to this query)
320
VMScore
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 6.0
Google Android 5.0
Google Android 5.1
668
VMScore
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
668
VMScore
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 6.0
Google Android 5.0
Google Android 5.1
445
VMScore
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
445
VMScore
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 6.0
Google Android 7.0
Google Android 5.1
445
VMScore
CVE-2017-18666
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software. Applications can send arbitrary premium SMS messages. The Samsung ID is SVE-2017-8701 (June 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 4.4
Google Android 7.1.1
Google Android 5.1
436
VMScore
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
694
VMScore
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
668
VMScore
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
312
VMScore
CVE-2017-18695
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.0) software. Attackers (who control a certain subdomain) can discover a user's credentials, during an email account login, via an EAS autodiscover packet. The Samsung ID is SVE-2016-7654 (Jan...
Google Android 6.0
Google Android 7.0
Google Android 5.0
Google Android 4.4
Google Android 5.1
VMScore
CVSSv2
CVSSv3
VMScore
Recommendations:
CVE-2024-23692
CVE-2012-1823
memory leak
CVE-2024-0627
CVE-2024-31402
privilege escalation
CVE-2024-36418
remote code execution
CVE-2024-27844
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
« PREV
1
2
3
4
5
6
7
8
NEXT »