QSEE information disclosure via unchecked image address
Published Jun 9, 2021 · Updated Aug 4, 2024
Buffer over-read in Qualcomm Snapdragon Wired Infrastructure and Networking allows local users to disclose protected QSEE information. WIN TZ firmware dereferences an image address before checking that the address falls within the permitted range, causing an out-of-bounds read. Local code execution on an affected chipset is required, and the documented consequence is QSEE information disclosure rather than data modification.
Summary
What happened
Buffer over-read in Qualcomm Snapdragon Wired Infrastructure and Networking allows local users to disclose protected QSEE information. WIN TZ firmware dereferences an image address before checking that the address falls within the permitted range, causing an out-of-bounds read. Local code execution on an affected chipset is required, and the documented consequence is QSEE information disclosure rather than data modification.
The record
- CVE
- CVE-2020-11266
- Published
- Jun 9, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-126, T1005
- 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.
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