Memory corruption via unterminated HLOS string copy
Published Jan 21, 2020 · Updated Aug 5, 2024
Memory corruption in the Qualcomm Snapdragon kernel allows local users to corrupt memory by supplying non-NUL-terminated HLOS data. The kernel copies HLOS-supplied string data without first validating that the input has a terminating NUL byte, leaving the copy without a validated termination boundary. Exploitation requires low-privileged local execution on an affected chipset; Qualcomm has not published the exact kernel function or a narrower operational consequence.
Summary
What happened
Memory corruption in the Qualcomm Snapdragon kernel allows local users to corrupt memory by supplying non-NUL-terminated HLOS data. The kernel copies HLOS-supplied string data without first validating that the input has a terminating NUL byte, leaving the copy without a validated termination boundary. Exploitation requires low-privileged local execution on an affected chipset; Qualcomm has not published the exact kernel function or a narrower operational consequence.
The record
- CVE
- CVE-2019-14023
- Published
- Jan 21, 2020
- Updated
- Aug 5, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 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=MDM9607, Nicobar, Rennell, SA6155P, SDX55, SM6150, SM7150, SM8150, SM8250, SXR2130
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
No sourced classifications are available.
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