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)
9.8
CVSSv3
CVE-2018-21066
An issue exists on Samsung mobile devices with M(6.0) (Exynos or MediaTek chipsets) software. There is a buffer overflow in a Trustlet that can cause memory corruption. The Samsung ID is SVE-2018-11599 (July 2018).
Google Android 6.0
7.3
CVSSv3
CVE-2018-21071
An issue exists on Samsung mobile devices with M(6.0) software. Because of an unprotected intent, an attacker can read arbitrary files and emails, and take over an email account. The Samsung ID is SVE-2018-11633 (May 2018).
Google Android 6.0
3.3
CVSSv3
CVE-2018-21074
An issue exists on Samsung mobile devices with M(6.x) (Exynos or Qualcomm chipsets) software. There is information disclosure from a Trustlet via the debug log. The Samsung ID is SVE-2017-10638 (April 2018).
Google Android 6.0
Google Android 6.0.1
7.5
CVSSv3
CVE-2018-21083
An issue exists on Samsung mobile devices with M(6.0), N(7.x), and O(8.0) (Exynos or Qualcomm chipsets) software. There is information disclosure (of a kernel address) via trustonic_tee. The Samsung ID is SVE-2017-11175 (February 2018).
Google Android 6.0
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
Google Android 8.0
8.1
CVSSv3
CVE-2018-21084
An issue exists on Samsung mobile devices with L(5.1), M(6.0), and N(7.x) software. There is a race condition with a resultant read-after-free issue in get_kek. The Samsung ID is SVE-2017-11174 (February 2018).
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
8.1
CVSSv3
CVE-2018-21085
An issue exists on Samsung mobile devices with L(5.x), M(6.0), and N(7.x) software. There is a race condition with a resultant use-after-free in vnswap_deinit_backing_storage. The Samsung ID is SVE-2017-11176 (February 2018).
Google Android 5.0
Google Android 5.0.1
Google Android 5.0.2
Google Android 5.1
Google Android 5.1.0
Google Android 5.1.1
Google Android 6.0
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
8.1
CVSSv3
CVE-2018-21086
An issue exists on Samsung mobile devices with L(5.x), M(6.0), and N(7.x) software. There is a race condition with a resultant double free in vnswap_init_backing_storage. The Samsung ID is SVE-2017-11177 (February 2018).
Google Android 5.0
Google Android 5.0.1
Google Android 5.0.2
Google Android 5.1
Google Android 5.1.0
Google Android 5.1.1
Google Android 6.0
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
9.8
CVSSv3
CVE-2018-21087
An issue exists on Samsung mobile devices with L(5.x), M(6.x), and N(7.x) software. There is a vnswap heap-based buffer overflow via the store function, with resultant privilege escalation. The Samsung ID is SVE-2017-10599 (January 2018).
Google Android 5.0
Google Android 5.0.1
Google Android 5.0.2
Google Android 5.1
Google Android 5.1.0
Google Android 5.1.1
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
CVSSv3
CVSSv2
CVSSv3
VMScore
Recommendations:
authentication bypass
CVE-2024-30051
remote
CVE-2024-27954
CVE-2023-51483
CVE-2023-47782
SSRF
CVE-2024-24715
CVE-2023-52424
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
« PREV
1
2
3
4
5
6
7
NEXT »