Secure resource access via unchecked AP-S lock bit
Published Sep 2, 2022 · Updated Aug 4, 2024
Improper input validation in Qualcomm Snapdragon firmware allows physically proximate attackers to read and write secure resources. The Core permission-verification logic does not properly check the AP-S lock bit when validating secure resource group permissions. Physical access to an affected chipset is required, and successful exploitation exposes protected data to non-secure reads and modification.
Summary
What happened
Improper input validation in Qualcomm Snapdragon firmware allows physically proximate attackers to read and write secure resources. The Core permission-verification logic does not properly check the AP-S lock bit when validating secure resource group permissions. Physical access to an affected chipset is required, and successful exploitation exposes protected data to non-secure reads and modification.
The record
- CVE
- CVE-2021-35108
- Published
- Sep 2, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-754
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2022CVE 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