Memory corruption via graphics allocation integer overflow
Published Apr 1, 2024 · Updated Aug 12, 2024
Integer overflow in Qualcomm Snapdragon graphics firmware allows local users to corrupt memory through a crafted graphics allocation request. The published CWE mapping establishes an integer-overflow-to-buffer-overflow chain during graphics memory allocation, but Qualcomm names no function or interface. Local access is required; successful corruption can compromise confidentiality, integrity, and availability without user interaction.
Summary
What happened
Integer overflow in Qualcomm Snapdragon graphics firmware allows local users to corrupt memory through a crafted graphics allocation request. The published CWE mapping establishes an integer-overflow-to-buffer-overflow chain during graphics memory allocation, but Qualcomm names no function or interface. Local access is required; successful corruption can compromise confidentiality, integrity, and availability without user interaction.
The record
- CVE
- CVE-2024-21470
- Published
- Apr 1, 2024
- Updated
- Aug 12, 2024
- Vendor
- Qualcomm
- Product
- WSA8810 Firmware
- Classifications
- CWE-190, CWE-680
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2024CVE publishedPublication date reported by the CVE source.
- Aug 12, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=*
What conditions does exploitation require?
What is affected?
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