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.
Project Subscriptions
| Vendors | Products |
|---|---|
|
Qualcomm
Subscribe
|
Ipq4019
Subscribe
Ipq4019 Firmware
Subscribe
Mdm9206
Subscribe
Mdm9206 Firmware
Subscribe
Mdm9607
Subscribe
Mdm9607 Firmware
Subscribe
Mdm9635m
Subscribe
Mdm9635m Firmware
Subscribe
Mdm9640
Subscribe
Mdm9640 Firmware
Subscribe
Mdm9645
Subscribe
Mdm9645 Firmware
Subscribe
Msm8909w
Subscribe
Msm8909w Firmware
Subscribe
Sd 205
Subscribe
Sd 205 Firmware
Subscribe
Sd 210
Subscribe
Sd 210 Firmware
Subscribe
Sd 212
Subscribe
Sd 212 Firmware
Subscribe
Sd 400
Subscribe
Sd 400 Firmware
Subscribe
Sd 410
Subscribe
Sd 410 Firmware
Subscribe
Sd 412
Subscribe
Sd 412 Firmware
Subscribe
Sd 415
Subscribe
Sd 415 Firmware
Subscribe
Sd 615
Subscribe
Sd 615 Firmware
Subscribe
Sd 616
Subscribe
Sd 616 Firmware
Subscribe
Sd 800
Subscribe
Sd 800 Firmware
Subscribe
Sd 810
Subscribe
Sd 810 Firmware
Subscribe
|
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2015-9061 | 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. |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: qualcomm
Published:
Updated: 2024-09-16T19:10:08.563Z
Reserved: 2017-08-16T00:00:00.000Z
Link: CVE-2015-9208
No data.
Status : Modified
Published: 2018-04-18T14:29:08.323
Modified: 2024-11-21T02:40:03.130
Link: CVE-2015-9208
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD