PT-2024-28461 · Samsung · Samsung Modem +1

Name of the Vulnerable Software and Affected Versions: Samsung Exynos versions 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110 Samsung Modem versions 5123, 5300 Description: The baseband software does not properly check the length specified by the MM Mobility Management module, which can lead to...

CVE-2024-39343

An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, Modem 5123, and Modem 5300. The baseband software does not properly check the length specified by the MM Mobility Management module, which can lead to Denial of Servic...

CVE-2024-39890

An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, W1000, Modem 5123, Modem 5300. The baseband software does not properly check the length specified by the CC Call...

CVE-2024-39343

An issue was discovered in Samsung Mobile Processor and Wearable Processor Exynos 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, Modem 5123, and Modem 5300. The baseband software does not properly check the length specified by the MM Mobility Management module, which can lead to Denial of Servic...

Samsung Mobile Processor 安全漏洞

SAMSUNG Mobile Processor is a family of mobile processors from the South Korean company Samsung SAMSUNG. A security vulnerability exists in Samsung Mobile Processor that originates from the baseband software not properly checking the length of the CC designation, which can lead to out-of-bounds...

CVE-2024-39343

CVE-2024-39343 affects Samsung’s Mobile Processor and Wearable Processor baseband (Exynos 2100/1280/2200/1330/1380/1480/2400/9110 and Modem 5123/5300). The root cause is that baseband software does not properly validate the length specified by the Mobility Management (MM) module, which can lead t...

CVE-2024-39890

CVE-2024-39890 affects Samsung baseband software in multiple Exynos lines (Mobile Processor, Wearable Processor, Modem) including Exynos 980–9825, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920/W930/W1000, as well as Modems 5123 and 5300. The issue is that the baseband does ...

PT-2024-28712 · Samsung · Samsung Exynos Modem +2

Name of the Vulnerable Software and Affected Versions: Samsung Exynos versions 980 through 9825 Samsung Exynos versions 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110 Samsung Exynos Modem versions 5123, 5300 Samsung Exynos Wearable Processor versions W920, W930, W1000 Description:...

PUB-A-355817499

In GetCellInfoList of protocolnetadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...

CVE-2024-53980 Spoofed length byte traps CC2538 in endless loop

RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things IoT devices and other embedded devices. A malicious actor can send a IEEE 802.15.4 packet with spoofed length byte and optionally spoofed FCS, which eventually results into an endless...

CVE-2024-47019

In ProtocolEmbmsSaiListAdapter::Init of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...

CVE-2024-47019

In ProtocolEmbmsSaiListAdapter::Init of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...

CVE-2024-47019

In ProtocolEmbmsSaiListAdapter::Init of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...

CVE-2024-47019

CVE-2024-47019 affects Google Pixel devices via a buffer/read bounds issue in ProtocolEmbmsSaiListAdapter::Init() inside protocolembmsadapter.cpp. The vulnerability is an out-of-bounds read caused by a missing bounds check, potentially leading to local information disclosure and baseband firmware...

CVE-2024-47015

In ProtocolMiscHwConfigChangeAdapter::GetData of protocolmiscadapter.cpp, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...

CVE-2024-47015

CVE-2024-47015 affects Google Pixel devices via the function ProtocolMiscHwConfigChangeAdapter::GetData() in protocolmiscadapter.cpp. The vulnerability is caused by a missing bounds check, leading to a possible out-of-bounds read and local information disclosure. Impact is stated as requiring bas...

CVE-2024-47015

In ProtocolMiscHwConfigChangeAdapter::GetData of protocolmiscadapter.cpp, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...

PT-2024-32342 · Google · Android

Name of the Vulnerable Software and Affected Versions: No specific software or version is mentioned. Description: The issue is related to a possible out-of-bounds read in the ProtocolMiscHwConfigChangeAdapter::GetData function, located in protocolmiscadapter.cpp. This could lead to local...

Google Adds New Pixel Security Features to Block 2G Exploits and Baseband Attacks

Google has revealed the various security guardrails that have been incorporated into its latest Pixel devices to counter the rising threat posed by baseband security attacks. The cellular baseband i.e., modem refers to a processor on the device that's responsible for handling all connectivity, su...

PUB-A-331666405

In ProtocolEmbmsSaiListAdapter::Init of protocolembmsadapter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with baseband firmware compromise required. User Interaction is not needed for exploitation...