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)
7.5
CVSSv3
CVE-2017-18643
An issue exists on Samsung mobile devices with M(6.x) and N(7.x) software. There is information disclosure of the kbase_context address of a GPU memory node. The Samsung ID is SVE-2017-8907 (December 2017).
Google Android 6.0
Google Android 6.0.1
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
7.5
CVSSv3
CVE-2018-21091
An issue exists on Samsung mobile devices with M(6.x) and N(7.x) software. Telecom has a System Crash via abnormal exception handling. The Samsung ID is SVE-2017-10906 (January 2018).
Google Android 6.0
Google Android 6.0.1
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
6.5
CVSSv3
CVE-2018-21092
An issue exists on Samsung mobile devices with M(6.x) and N(7.x) software. A crafted AT command may be sent by the DeviceTest application via an NFC tag. The Samsung ID is SVE-2017-10885 (January 2018).
Google Android 6.0
Google Android 6.0.1
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
4.6
CVSSv3
CVE-2017-18646
An issue exists on Samsung mobile devices with M(6.x) and N(7.x) software. An attacker can bypass the password requirement for tablet user switching by folding the magnetic cover. The Samsung ID is SVE-2017-10602 (December 2017).
Google Android 6.0
Google Android 6.0.1
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
7.5
CVSSv3
CVE-2017-18651
An issue exists on Samsung mobile devices with M(6.x) and N(7.x) software. There is an Integer Overflow in process_M_SetTokenTUIPasswd during handling of a trusted application, leading to memory corruption. The Samsung IDs are SVE-2017-9008 and SVE-2017-9009 (October 2017).
Google Android 6.0
Google Android 6.0.1
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
5.3
CVSSv3
CVE-2017-18658
An issue exists on Samsung mobile devices with M(6.0) software. The multiwindow_facade API allows malicious users to cause a NullPointerException and system halt via an attempted screen touch of a non-existing display. The Samsung ID is SVE-2017-9383 (August 2017).
Google Android 6.0
5.3
CVSSv3
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 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
4.3
CVSSv3
CVE-2017-18667
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 prevent users from learning that SMS storage space has been exhausted. The Samsung ID is SVE-2017-8702 (June 2017).
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.5
CVSSv3
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
CVSSv3
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
CVSSv3
CVSSv2
CVSSv3
VMScore
Recommendations:
CVE-2023-49333
CVE-2024-33901
CVE-2024-36001
CVE-2024-2835
firewall
XPath injection
authentication bypass
CVE-2024-22120
CVE-2024-32002
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 »