Vulnerabilities · 2016 · Google
CVE-2016-5349
Google Android vulnerability
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.
Affected products
Android. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Android runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- source.android.com/security/bulletin/2017-04-01 · Vendor Advisory
- www.qualcomm.com/company/product-security/security-advisories · Vendor Advisory
- www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access · Patch
- www.securityfocus.com/bid/97364 · Third Party Advisory
- www.securitytracker.com/id/1038201
- nvd.nist.gov/vuln/detail/CVE-2016-5349
- cve.org/CVERecord?id=CVE-2016-5349
More vulnerabilities in Google products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.