Malicious firmware loading via improper update verification
Published Mar 24, 2020 · Updated Aug 4, 2024
Improper firmware verification in Samsung mobile devices running Android 8.x, 9.0, or 10.0 allows attackers to load malicious touch-screen firmware. The touch-screen update path accepts firmware supplied through its kernel sysfs command interface without validating its authenticity. Public material does not establish the access needed to reach that path; demonstrated malformed firmware caused touch failures and I/O errors.
Summary
What happened
Improper firmware verification in Samsung mobile devices running Android 8.x, 9.0, or 10.0 allows attackers to load malicious touch-screen firmware. The touch-screen update path accepts firmware supplied through its kernel sysfs command interface without validating its authenticity. Public material does not establish the access needed to reach that path; demonstrated malformed firmware caused touch failures and I/O errors.
The record
- CVE
- CVE-2020-10831
- Published
- Mar 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-345, T1495
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 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?
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
- Android Firmware Exploitation – Unsigned Firmware in Samsung’s SoCproof of concept · demonstrated
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