| Title | Qualcomm Secure Execution Environment における情報漏えいに関する脆弱性 |
|---|---|
| Summary | Qualcomm Secure Execution Environment (QSEE) には、Linux Android などの high level operating systems (HLOS) からメモリアドレス情報を受け取る際、情報漏えいに関する脆弱性が存在します。 |
| Possible impacts | 情報を取得される可能性があります。 |
| Solution | ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。 |
| Publication Date | June 1, 2016, midnight |
| Registration Date | May 11, 2017, 2:29 p.m. |
| Last Update | May 11, 2017, 2:29 p.m. |
| CVSS3.0 : 警告 | |
| Score | 5.5 |
|---|---|
| Vector | CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| CVSS2.0 : 警告 | |
| Score | 4.3 |
|---|---|
| Vector | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| Android |
| No | Changed Details | Date of change |
|---|---|---|
| 0 | [2017年05月11日] 掲載 |
Feb. 17, 2018, 10:37 a.m. |
| Summary | The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure Execution Environment (QSEE) only write to legitimate memory ranges related to the QSEE secure application's HLOS client. When secure applications inside Qualcomm Secure Execution Environment (QSEE) receive memory addresses from a high level operating system (HLOS) such as Linux Android, those address have previously been verified as belonging to HLOS memory space rather than QSEE memory space, but they were not verified to be from HLOS user space rather than kernel space. This lack of verification could lead to privilege escalation within the HLOS. |
|---|---|
| Publication Date | April 7, 2017, 4:59 a.m. |
| Registration Date | Jan. 26, 2021, 2:13 p.m. |
| Last Update | Nov. 21, 2024, 11:54 a.m. |
| Configuration1 | or higher | or less | more than | less than | |
| cpe:2.3:o:google:android:*:*:*:*:*:*:*:* | 7.1.1 | ||||