Memory corruption via unchecked WLAN command copy
Published Aug 8, 2023 · Updated Aug 2, 2024
A classic buffer overflow in Qualcomm Snapdragon WLAN firmware allows local administrators to corrupt memory through a driver command. The doDriverCmd path copies an unspecified command without validating its size against the destination buffer. High-privileged local access is required, and Qualcomm has not disclosed the command format, destination buffer, or resulting post-corruption behavior.
Summary
What happened
A classic buffer overflow in Qualcomm Snapdragon WLAN firmware allows local administrators to corrupt memory through a driver command. The doDriverCmd path copies an unspecified command without validating its size against the destination buffer. High-privileged local access is required, and Qualcomm has not disclosed the command format, destination buffer, or resulting post-corruption behavior.
The record
- CVE
- CVE-2023-21649
- Published
- Aug 8, 2023
- Updated
- Aug 2, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-787, CWE-120
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 8, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
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