Memory corruption via unchecked RAM partition count
Published Jan 3, 2022 · Updated Aug 3, 2024
Out-of-bounds write in Qualcomm Snapdragon platforms allows local users to corrupt memory through a crafted RAM partition count. Core code accepts the supplied number of RAM partitions without validating that the count fits the partition table, enabling a write past its bounds. Local access is required, and Qualcomm has not disclosed whether successful corruption causes a crash or code execution.
Summary
What happened
Out-of-bounds write in Qualcomm Snapdragon platforms allows local users to corrupt memory through a crafted RAM partition count. Core code accepts the supplied number of RAM partitions without validating that the count fits the partition table, enabling a write past its bounds. Local access is required, and Qualcomm has not disclosed whether successful corruption causes a crash or code execution.
The record
- CVE
- CVE-2021-30282
- Published
- Jan 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-129
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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