Memory corruption via malformed file hash
Published Apr 1, 2022 · Updated Aug 4, 2024
Buffer overflow in Qualcomm Snapdragon Connectivity and Snapdragon Mobile allows local users to corrupt memory through a malformed file. The closed-source component improperly validates a file hash segment before using it during memory allocation, allowing the allocated buffer to overflow. Local access to a crafted file is required; public records do not identify the affected function or establish whether exploitation yields code execution, disclosure, or a service interruption.
Summary
What happened
Buffer overflow in Qualcomm Snapdragon Connectivity and Snapdragon Mobile allows local users to corrupt memory through a malformed file. The closed-source component improperly validates a file hash segment before using it during memory allocation, allowing the allocated buffer to overflow. Local access to a crafted file is required; public records do not identify the affected function or establish whether exploitation yields code execution, disclosure, or a service interruption.
The record
- CVE
- CVE-2021-35110
- Published
- Apr 1, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-704
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 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.
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