TrustZone memory corruption via unchecked pointer arguments
Published Jun 9, 2021 · Updated Aug 4, 2024
Memory corruption in TrustZone BSP for Qualcomm Snapdragon Wired Infrastructure and Networking allows local users to corrupt secure firmware memory. The BSP accepts pointer arguments without validating that their offsets remain within the permitted memory range before dereferencing them. Unauthenticated local access is sufficient; Qualcomm does not disclose whether exploitation yields code execution, data access, or only a service interruption.
Summary
What happened
Memory corruption in TrustZone BSP for Qualcomm Snapdragon Wired Infrastructure and Networking allows local users to corrupt secure firmware memory. The BSP accepts pointer arguments without validating that their offsets remain within the permitted memory range before dereferencing them. Unauthenticated local access is sufficient; Qualcomm does not disclose whether exploitation yields code execution, data access, or only a service interruption.
The record
- CVE
- CVE-2020-11259
- Published
- Jun 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-823
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo