Vulmon
Recent Vulnerabilities
Product List
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
google android 5.0 vulnerabilities and exploits
(subscribe to this query)
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
445
VMScore
CVE-2017-18659
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software. Attackers can crash system processes via a broadcast to AdaptiveDisplayColorService. The Samsung ID is SVE-2017-8290 (July 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
445
VMScore
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 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
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
356
VMScore
CVE-2017-18653
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.x) software. The Email application allows malicious users to send emails on behalf of any user via a broadcasted intent. The Samsung ID is SVE-2017-9357 (September 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
668
VMScore
CVE-2017-18693
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), M(6.0), and N(7.0) software. There is a buffer overflow in the fps sysfs entry. The Samsung ID is SVE-2016-7510 (January 2017).
Google Android 6.0
Google Android 7.0
Google Android 5.0
Google Android 4.4
Google Android 5.1
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
694
VMScore
CVE-2016-11031
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), and M(6.0) software. AntService allows a system_server crash and reboot. The Samsung ID is SVE-2016-7044 (November 2016).
Google Android 6.0
Google Android 5.0
Google Android 4.4
Google Android 5.1
694
VMScore
CVE-2016-11039
An issue exists on Samsung mobile devices with KK(4.4), L(5.0/5.1), and M(6.0) (AP + CP MDM9x35, or Qualcomm Onechip) software. There is a NULL pointer dereference issue in the IPC socket code. The Samsung ID is SVE-2016-5980 (July 2016).
Google Android 6.0
Google Android 5.0
Google Android 4.4
Google Android 5.1
187
VMScore
CVE-2016-11040
An issue exists on Samsung mobile devices with L(5.0/5.1) (with USB OTG MyFile2014_L_ESS support) software. There is a Factory Reset Protection (FRP) bypass. The Samsung ID is SVE-2015-5068 (June 2016).
Google Android 5.0
Google Android 5.1
VMScore
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
NEXT »