Memory corruption via expired NFC stack storage
Published Jan 21, 2020 · Updated Aug 5, 2024
Memory corruption in Snapdragon NFC card emulation on listed chipsets allows local users with low privileges to access expired stack storage. The NFC card-emulation path accesses stack storage after its owning scope ends; Qualcomm has not disclosed the responsible function or trigger. Successful exploitation corrupts process memory, but public records establish no specific code-execution or crash outcome.
Summary
What happened
Memory corruption in Snapdragon NFC card emulation on listed chipsets allows local users with low privileges to access expired stack storage. The NFC card-emulation path accesses stack storage after its owning scope ends; Qualcomm has not disclosed the responsible function or trigger. Successful exploitation corrupts process memory, but public records establish no specific code-execution or crash outcome.
The record
- CVE
- CVE-2019-14024
- Published
- Jan 21, 2020
- Updated
- Aug 5, 2024
- Vendor
- Qualcomm
- Product
- Snapdragon
- Classifications
- CWE-416
- 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=MSM8917, MSM8953, Nicobar, QM215, Rennell, SDM429, SDM439, SDM450, SDM632, SDM670, SDM710, SDM845, 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
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