Local device compromise via QMI allocation overflow
Published Mar 4, 2024 · Updated Aug 26, 2024
Memory corruption in Qualcomm Core Services firmware allows local users to compromise device confidentiality, integrity, and availability. A QMI request for memory from a DHMS-supported subsystem triggers an integer overflow in the allocation path, causing memory corruption. Exploitation requires local low-privileged access to an affected Qualcomm platform; no remote attack path or safer bounded consequence is published.
Summary
What happened
Memory corruption in Qualcomm Core Services firmware allows local users to compromise device confidentiality, integrity, and availability. A QMI request for memory from a DHMS-supported subsystem triggers an integer overflow in the allocation path, causing memory corruption. Exploitation requires local low-privileged access to an affected Qualcomm platform; no remote attack path or safer bounded consequence is published.
The record
- CVE
- CVE-2023-43550
- Published
- Mar 4, 2024
- Updated
- Aug 26, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-190
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 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