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 applications 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.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Android | * | 7.1.1 (including) | |
| Linux-flo | Ubuntu | esm-apps/xenial | * |
| Linux-flo | Ubuntu | trusty | * |
| Linux-flo | Ubuntu | vivid/stable-phone-overlay | * |
| Linux-flo | Ubuntu | xenial | * |
| Linux-flo | Ubuntu | yakkety | * |
| Linux-goldfish | Ubuntu | trusty | * |
| Linux-grouper | Ubuntu | trusty | * |
| Linux-linaro-omap | Ubuntu | precise | * |
| Linux-linaro-shared | Ubuntu | precise | * |
| Linux-linaro-vexpress | Ubuntu | precise | * |
| Linux-lts-quantal | Ubuntu | precise | * |
| Linux-lts-quantal | Ubuntu | precise/esm | * |
| Linux-lts-raring | Ubuntu | precise | * |
| Linux-lts-raring | Ubuntu | precise/esm | * |
| Linux-lts-saucy | Ubuntu | precise | * |
| Linux-lts-saucy | Ubuntu | precise/esm | * |
| Linux-lts-utopic | Ubuntu | trusty | * |
| Linux-lts-wily | Ubuntu | trusty | * |
| Linux-maguro | Ubuntu | trusty | * |
| Linux-mako | Ubuntu | esm-apps/xenial | * |
| Linux-mako | Ubuntu | trusty | * |
| Linux-mako | Ubuntu | vivid/stable-phone-overlay | * |
| Linux-mako | Ubuntu | xenial | * |
| Linux-mako | Ubuntu | yakkety | * |
| Linux-manta | Ubuntu | trusty | * |
| Linux-qcm-msm | Ubuntu | precise | * |
| Linux-raspi2 | Ubuntu | vivid/ubuntu-core | * |
There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:
Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:
Information exposures can occur in different ways:
It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.