Local memory corruption via unbounded template count
Published Mar 5, 2020 · Updated Aug 5, 2024
A stack-based buffer overflow in Qualcomm Snapdragon fingerprint firmware allows local users to corrupt memory during identification initialization. The identification stage fails to check the supplied number of templates before initializing them, causing writes beyond a stack buffer. Local access to the fingerprint component is required; published sources report memory corruption but do not disclose whether code execution is attainable.
Summary
What happened
A stack-based buffer overflow in Qualcomm Snapdragon fingerprint firmware allows local users to corrupt memory during identification initialization. The identification stage fails to check the supplied number of templates before initializing them, causing writes beyond a stack buffer. Local access to the fingerprint component is required; published sources report memory corruption but do not disclose whether code execution is attainable.
The record
- CVE
- CVE-2019-14015
- Published
- Mar 5, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-120
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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