Local device compromise via unchecked FRS/UDS buffer lengths
Published Oct 7, 2024 · Updated Oct 7, 2024
Memory corruption in HLOS firmware on Qualcomm Snapdragon platforms allows local users to compromise confidentiality, integrity, and availability. FRS/UDS request and response buffer handling accepts an invalid length supplied by HLOS and performs memory operations outside the intended buffer bounds. A local low-privileged HLOS context is required; successful exploitation can expose or alter protected data and interrupt device operation.
Summary
What happened
Memory corruption in HLOS firmware on Qualcomm Snapdragon platforms allows local users to compromise confidentiality, integrity, and availability. FRS/UDS request and response buffer handling accepts an invalid length supplied by HLOS and performs memory operations outside the intended buffer bounds. A local low-privileged HLOS context is required; successful exploitation can expose or alter protected data and interrupt device operation.
The record
- CVE
- CVE-2024-23369
- Published
- Oct 7, 2024
- Updated
- Oct 7, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2024CVE publishedPublication date reported by the CVE source.
- Oct 7, 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