Local memory corruption via stale buffer size
Published May 6, 2024 · Updated Aug 1, 2024
Stack-based buffer overflow in Qualcomm Snapdragon PMIC firmware allows local users to corrupt memory through an affected chipset. PMIC code carries a buffer size forward from a previous call and reuses it without validating or reinitializing the value before a later buffer operation. Local access is required; exploitation needs no prior privileges or user interaction and can read or alter protected data and interrupt device operation.
Summary
What happened
Stack-based buffer overflow in Qualcomm Snapdragon PMIC firmware allows local users to corrupt memory through an affected chipset. PMIC code carries a buffer size forward from a previous call and reuses it without validating or reinitializing the value before a later buffer operation. Local access is required; exploitation needs no prior privileges or user interaction and can read or alter protected data and interrupt device operation.
The record
- CVE
- CVE-2024-21474
- Published
- May 6, 2024
- Updated
- Aug 1, 2024
- Vendor
- Qualcomm
- Product
- QCA6698AQ Firmware
- Classifications
- CWE-787, CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=-
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.
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