Filtered by vendor Samsung
Subscriptions
Total
1183 CVE
CVE | Vendors | Products | Updated | CVSS v3.1 |
---|---|---|---|---|
CVE-2024-49401 | 1 Samsung | 1 Android | 2024-11-12 | 5.1 Medium |
Improper input validation in Settings Suggestions prior to SMR Nov-2024 Release 1 allows local attackers to launch privileged activities. | ||||
CVE-2024-34679 | 1 Samsung | 1 Android | 2024-11-12 | 4 Medium |
Incorrect default permissions in Crane prior to SMR Nov-2024 Release 1 allows local attackers to access files with phone privilege. | ||||
CVE-2024-34674 | 1 Samsung | 1 Android | 2024-11-12 | 4.6 Medium |
Improper access control in Contacts prior to SMR Nov-2024 Release 1 allows physical attackers to access data across multiple user profiles. | ||||
CVE-2024-34675 | 1 Samsung | 1 Android | 2024-11-12 | 2.4 Low |
Improper access control in Dex Mode prior to SMR Nov-2024 Release 1 allows physical attackers to temporarily access to unlocked screen. | ||||
CVE-2024-34677 | 1 Samsung | 1 Android | 2024-11-12 | 4 Medium |
Exposure of sensitive information in System UI prior to SMR Nov-2024 Release 1 allow local attackers to make malicious apps appear as legitimate. | ||||
CVE-2024-34680 | 1 Samsung | 1 Android | 2024-11-12 | 4 Medium |
Use of implicit intent for sensitive communication in WlanTest prior to SMR Nov-2024 Release 1 allows local attackers to get sensitive information. | ||||
CVE-2024-34676 | 1 Samsung | 1 Android | 2024-11-12 | 4.4 Medium |
Out-of-bounds write in parsing subtitle file in libsubextractor.so prior to SMR Nov-2024 Release 1 allows local attackers to cause memory corruption. User interaction is required for triggering this vulnerability. | ||||
CVE-2024-34678 | 1 Samsung | 1 Android | 2024-11-12 | 5.9 Medium |
Out-of-bounds write in libsapeextractor.so prior to SMR Nov-2024 Release 1 allows local attackers to cause memory corruption. | ||||
CVE-2024-49402 | 1 Samsung | 1 Android | 2024-11-12 | 4.6 Medium |
Improper input validation in Dressroom prior to SMR Nov-2024 Release 1 allow physical attackers to access data across multiple user profiles. | ||||
CVE-2024-34669 | 1 Samsung | 1 Android | 2024-11-01 | 7.5 High |
Out-of-bounds write in parsing h.263+ format in librtppayload.so prior to SMR Oct-2024 Release 1 allows remote attackers to execute arbitrary code with system privilege. User interaction is required for triggering this vulnerability. | ||||
CVE-2024-34668 | 2 Samsung, Samsung Mobile | 2 Android, Samsung Mobile Devices | 2024-10-30 | 7.5 High |
Out-of-bounds write in parsing h.263 format in librtppayload.so prior to SMR Oct-2024 Release 1 allows remote attackers to execute arbitrary code with system privilege. User interaction is required for triggering this vulnerability. | ||||
CVE-2024-34667 | 2 Samsung, Samsung Mobile | 2 Android, Samsung Mobile Devices | 2024-10-30 | 7.5 High |
Out-of-bounds write in parsing h.265 format in librtppayload.so prior to SMR Oct-2024 Release 1 allows remote attackers to execute arbitrary code with system privilege. User interaction is required for triggering this vulnerability. | ||||
CVE-2024-34666 | 2 Samsung, Samsung Mobile | 2 Android, Samsung Mobile Devices | 2024-10-30 | 7.5 High |
Out-of-bounds write in parsing h.264 format in a specific mode in librtppayload.so prior to SMR Oct-2024 Release 1 allows remote attackers to execute arbitrary code with system privilege. User interaction is required for triggering this vulnerability. | ||||
CVE-2024-34665 | 2 Samsung, Samsung Mobile | 2 Android, Samsung Mobile Devices | 2024-10-30 | 7.5 High |
Out-of-bounds write in parsing h.264 format in librtppayload.so prior to SMR Oct-2024 Release 1 allows remote attackers to execute arbitrary code with system privilege. User interaction is required for triggering this vulnerability. | ||||
CVE-2024-44068 | 1 Samsung | 6 Exynos 850 Firmware, Exynos 980 Firmware, Exynos 9820 Firmware and 3 more | 2024-10-10 | 8.1 High |
An issue was discovered in the m2m scaler driver in Samsung Mobile Processor and Wearable Processor Exynos 9820, 9825, 980, 990, 850,and W920. A Use-After-Free in the mobile processor leads to privilege escalation. | ||||
CVE-2024-31960 | 2 Samsung, Samsung Mobile | 5 Exynos 1480, Exynos 1480 Firmware, Exynos 2400 and 2 more | 2024-09-24 | 7.8 High |
An issue was discovered in Samsung Mobile Processor Exynos 1480, Exynos 2400. The xclipse amdgpu driver has a reference count bug. This can lead to a use after free. | ||||
CVE-2024-27365 | 1 Samsung | 18 Exynos 1080, Exynos 1080 Firmware, Exynos 1280 and 15 more | 2024-09-20 | 4.4 Medium |
An issue was discovered in Samsung Mobile Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsi_rx_blockack_ind(), there is no input validation check on a length coming from userspace, which can lead to a potential heap over-read. | ||||
CVE-2024-5760 | 3 Hp Inc, Microsoft, Samsung | 3 Samsung Universal Print Driver, Windows, Universal Print Driver | 2024-09-13 | 8.4 High |
The Samsung Universal Print Driver for Windows is potentially vulnerable to escalation of privilege allowing the creation of a reverse shell in the tool. This is only applicable for products in the application released or manufactured before 2018. | ||||
CVE-2024-27364 | 1 Samsung | 18 Exynos 1080, Exynos 1080 Firmware, Exynos 1280 and 15 more | 2024-09-11 | 4.4 Medium |
An issue was discovered in Mobile Processor, Wearable Processor Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsi_rx_roamed_ind(), there is no input validation check on a length coming from userspace, which can lead to a potential heap over-read. | ||||
CVE-2024-27366 | 1 Samsung | 18 Exynos 1080, Exynos 1080 Firmware, Exynos 1280 and 15 more | 2024-09-11 | 4.4 Medium |
An issue was discovered in Samsung Mobile Processor, Wearable Processor Exynos Exynos 980, Exynos 850, Exynos 1080, Exynos 1280, Exynos 1380, Exynos 1330, Exynos 1480, Exynos W920, Exynos W930. In the function slsi_rx_scan_done_ind(), there is no input validation check on a length coming from userspace, which can lead to a potential heap over-read. |