Vulmon
Recent Vulnerabilities
Research Posts
Trends
Blog
About
Contact
Vulmon Alerts
By Relevance
By Risk Score
By Publish Date
samsung samsung mobile 7.0 vulnerabilities and exploits
(subscribe to this query)
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 4.4
Google Android 5.0
Google Android 5.1
Google Android 6.0
Google Android 7.0
187
VMScore
CVE-2018-21045
An issue exists on Samsung mobile devices with N(7.x) and O(8.x) software. There is Clipboard access in the lockscreen state via a copy-and-paste action. The Samsung ID is SVE-2018-13381 (December 2018).
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
Google Android 8.0
Google Android 8.1
294
VMScore
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
445
VMScore
CVE-2018-21059
An issue exists on Samsung mobile devices with N(7.x) and O(8.x) software. There is Clipboard content visibility in the locked state via the emergency contact picker. The Samsung ID is SVE-2018-11806 (September 2018).
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
Google Android 8.0
Google Android 8.1
668
VMScore
CVE-2018-21075
An issue exists on Samsung mobile devices with N(7.x) and O(8.x) software. The Call+ application can load classes from an unintended path, leading to Code Execution. The Samsung ID is SVE-2017-10886 (April 2018).
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
Google Android 8.0
Google Android 8.1
445
VMScore
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
605
VMScore
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
169
VMScore
CVE-2019-20623
An issue exists on Samsung mobile devices with N(7.1), O(8.x), and P(9.0) software. Gallery has uninitialized memory disclosure. The Samsung ID is SVE-2018-13060 (February 2019).
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
Google Android 8.0
Google Android 8.1
Google Android 9.0
187
VMScore
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
890
VMScore
CVE-2018-21050
An issue exists on Samsung mobile devices with N(7.x) and O(8.X) (Exynos chipsets) software. There is a Buffer overflow in the esecomm Trustlet, leading to arbitrary code execution. The Samsung ID is SVE-2018-12852 (October 2018).
Google Android 7.0
Google Android 7.1.0
Google Android 7.1.1
Google Android 7.1.2
Google Android 8.0
Google Android 8.1
VMScore
CVSSv2
CVSSv3
VMScore
Recommendations:
CVE-2024-22120
CVE-2024-35921
CVE-2024-35874
brute force
CVE-2024-36080
unprivileged
CVE-2024-35917
IDOR
CVE-2024-4947
Vulnerability Notification Service
You don’t have to wait for vulnerability scanning results
Get Started
« PREV
3
4
5
6
7
8
9
10
NEXT »