Privilege escalation via unchecked authentication result write
Published Mar 10, 2020 · Updated Aug 4, 2024
Out-of-bounds write in FPC Fingerprint TEE on the Android kernel allows local users with System privileges to elevate privileges. The get_auth_result function in fpc_ta_hw_auth.c writes authentication-result data without checking the destination bounds. Exploitation requires local System execution privileges and no user interaction, and successful memory corruption grants additional permissions.
Summary
What happened
Out-of-bounds write in FPC Fingerprint TEE on the Android kernel allows local users with System privileges to elevate privileges. The get_auth_result function in fpc_ta_hw_auth.c writes authentication-result data without checking the destination bounds. Exploitation requires local System execution privileges and no user interaction, and successful memory corruption grants additional permissions.
The record
- CVE
- CVE-2020-0011
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Fingerprint Cards AB
- Product
- FPC Fingerprint TEE
- Classifications
- CWE-787, T1068
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=Android kernel
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.
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