CVE-2016-5349
published 2017-04-06CVE-2016-5349: The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Secure…
PriorityP423medium5.5CVSS 3.0
AVLACLPRNUIRSUCHINAN
EPSS
1.00%
59.6th percentile
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
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| android | <= 7.1.1 | — | |
| android | — | — |
CVSS provenance
nvdv3.05.5MEDIUMCVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
osv5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-5c44-q7pc-hwjg: The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Sec
ghsa_unreviewed·2022-05-17
CVE-2016-5349 [MEDIUM] CWE-200 GHSA-5c44-q7pc-hwjg: The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Sec
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.
OSV
CVE-2016-5349: The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Sec
osv·2017-04-06·CVSS 5.5
CVE-2016-5349 [MEDIUM] CVE-2016-5349: The high level operating systems (HLOS) was not providing sufficient memory address information to ensure that secure applications inside Qualcomm Sec
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.
Android
CVE-2016-5349: Android Security Bulletin 2017-04-01
CVE: CVE-2016-5349
Severity: HIGH
References: A-29083830
QC-CR#1021945
[2]
[3]
[4]
vendor_android·2017-04-01·CVSS 5.5
CVE-2016-5349 [MEDIUM] CVE-2016-5349: Android Security Bulletin 2017-04-01
CVE: CVE-2016-5349
Severity: HIGH
References: A-29083830
QC-CR#1021945
[2]
[3]
[4]
Android Security Bulletin 2017-04-01
CVE: CVE-2016-5349
Severity: HIGH
References: A-29083830
QC-CR#1021945
[2]
[3]
[4]
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://www.securityfocus.com/bid/97364http://www.securitytracker.com/id/1038201https://source.android.com/security/bulletin/2017-04-01https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cvehttps://www.qualcomm.com/company/product-security/security-advisorieshttp://www.securityfocus.com/bid/97364http://www.securitytracker.com/id/1038201https://source.android.com/security/bulletin/2017-04-01https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cvehttps://www.qualcomm.com/company/product-security/security-advisories
2017-04-06
Published