Memory corruption via unchecked VM handshake copy
Published Sep 2, 2024 · Updated Sep 5, 2024
Memory corruption in Qualcomm Snapdragon computer-vision firmware allows local users to compromise confidentiality, integrity, and availability. During the Primary VM–Trusted VM handshake, the component copies handshake data without checking its size, corrupting memory. Low-privileged local access is required; Qualcomm has not disclosed the malformed field, target buffer, or exact post-corruption behavior.
Summary
What happened
Memory corruption in Qualcomm Snapdragon computer-vision firmware allows local users to compromise confidentiality, integrity, and availability. During the Primary VM–Trusted VM handshake, the component copies handshake data without checking its size, corrupting memory. Low-privileged local access is required; Qualcomm has not disclosed the malformed field, target buffer, or exact post-corruption behavior.
The record
- CVE
- CVE-2024-33054
- Published
- Sep 2, 2024
- Updated
- Sep 5, 2024
- Vendor
- Qualcomm
- Product
- Qualcomm WCN3660B Firmware
- Classifications
- CWE-120, CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 2, 2024CVE publishedPublication date reported by the CVE source.
- Sep 5, 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