In Android before 2018-04-05 or earlier security patch level on Qualcomm Snapdragon Mobile and Snapdragon Wear IPQ4019, MDM9206, MDM9607, MDM9635M, MDM9640, MDM9645, MSM8909W, SD 210/SD 212/SD 205, SD 400, SD 410/12, SD 615/16/SD 415, SD 800, and SD 810, the function tzbsp_pil_verify_sig() does not strictly check that the pointer to ELF and program headers and hash segment is within secure memory. It only checks that the address is not in non-secure memory. A given address range can overlap with both secure and non-secure regions - hence if such an address is passed in, it would not pass the non-secure range check, and would be considered valid by the function, even though that memory area could be modified by the non-secure side.
This vulnerability carries a CRITICAL severity rating with a CVSS v3.1 score of 9.8, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 36 products from qualcomm, from qualcomm, from qualcomm and 33 others, organizations running these solutions should prioritize assessment and patching.
First disclosed in 2018, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2018-04-18T14:29:08.323
2024-11-21T02:40:03.130
Modified
CVSSv3.0: 9.8 (CRITICAL)
AV:N/AC:L/Au:N/C:C/I:C/A:C
10.0
10.0
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Operating System | qualcomm | mdm9206_firmware | - | Yes |
| Hardware | qualcomm | mdm9206 | - | No |
| Operating System | qualcomm | mdm9607_firmware | - | Yes |
| Hardware | qualcomm | mdm9607 | - | No |
| Operating System | qualcomm | ipq4019_firmware | - | Yes |
| Hardware | qualcomm | ipq4019 | - | No |
| Operating System | qualcomm | mdm9635m_firmware | - | Yes |
| Hardware | qualcomm | mdm9635m | - | No |
| Operating System | qualcomm | mdm9640_firmware | - | Yes |
| Hardware | qualcomm | mdm9640 | - | No |
| Operating System | qualcomm | mdm9645_firmware | - | Yes |
| Hardware | qualcomm | mdm9645 | - | No |
| Operating System | qualcomm | msm8909w_firmware | - | Yes |
| Hardware | qualcomm | msm8909w | - | No |
| Operating System | qualcomm | sd_210_firmware | - | Yes |
| Hardware | qualcomm | sd_210 | - | No |
| Operating System | qualcomm | sd_212_firmware | - | Yes |
| Hardware | qualcomm | sd_212 | - | No |
| Operating System | qualcomm | sd_205_firmware | - | Yes |
| Hardware | qualcomm | sd_205 | - | No |
| Operating System | qualcomm | sd_400_firmware | - | Yes |
| Hardware | qualcomm | sd_400 | - | No |
| Operating System | qualcomm | sd_410_firmware | - | Yes |
| Hardware | qualcomm | sd_410 | - | No |
| Operating System | qualcomm | sd_412_firmware | - | Yes |
| Hardware | qualcomm | sd_412 | - | No |
| Operating System | qualcomm | sd_615_firmware | - | Yes |
| Hardware | qualcomm | sd_615 | - | No |
| Operating System | qualcomm | sd_616_firmware | - | Yes |
| Hardware | qualcomm | sd_616 | - | No |
| Operating System | qualcomm | sd_415_firmware | - | Yes |
| Hardware | qualcomm | sd_415 | - | No |
| Operating System | qualcomm | sd_800_firmware | - | Yes |
| Hardware | qualcomm | sd_800 | - | No |
| Operating System | qualcomm | sd_810_firmware | - | Yes |
| Hardware | qualcomm | sd_810 | - | No |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For qualcomm's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.