CVE-2016-5349
Last modified
CVE-2016-5349 is a vulnerability of currently unknown severity. 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. EPSS estimates a 1.00% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Android | <= 7.1.1 |
References
- http://www.securityfocus.com/bid/97364Third Party Advisory, VDB Entry
- https://source.android.com/security/bulletin/2017-04-01Vendor Advisory
- https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cveIssue Tracking, Patch, Third Party Advisory
- http://www.securityfocus.com/bid/97364Third Party Advisory, VDB Entry
- https://source.android.com/security/bulletin/2017-04-01Vendor Advisory
- https://www.codeaurora.org/insufficient-memory-address-information-prevent-arbitrary-memory-access-qsee-secure-applications-cveIssue Tracking, Patch, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-5349?
How severe is CVE-2016-5349?
How do I fix CVE-2016-5349?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-5343drivers/soc/qcom/qdsp6v2/voice_svc.c in the QDSP6v2 Voice Se…9.8
- CVE-2016-5344Multiple integer overflows in the MDSS driver for the Linux …9.8
- CVE-2016-5345Buffer overflow in the Qualcomm radio driver in Android befo…
- CVE-2016-5346An Information Disclosure vulnerability exists in the Google…5.5
- CVE-2016-5347In all Qualcomm products with Android releases from CAF usin…
- CVE-2016-5348The GPS component in Android 4.x before 4.4.4, 5.0.x before …
- CVE-2016-5350epan/dissectors/packet-dcerpc-spoolss.c in the SPOOLS compon…
- CVE-2016-5351epan/crypt/airpdcap.c in the IEEE 802.11 dissector in Wiresh…
- CVE-2016-5352epan/crypt/airpdcap.c in the IEEE 802.11 dissector in Wiresh…
- CVE-2016-5353epan/dissectors/packet-umts_fp.c in the UMTS FP dissector in…
- CVE-2016-5354The USB subsystem in Wireshark 1.12.x before 1.12.12 and 2.x…
- CVE-2016-5355wiretap/toshiba.c in the Toshiba file parser in Wireshark 1.…
Are you affected by CVE-2016-5349?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
