Unauthenticated kernel panic via Timaservice
Published Apr 7, 2020 · Updated Aug 5, 2024
Improper input validation in Samsung mobile devices running Android 7.0 allows remote attackers to trigger a kernel panic in Timaservice. Samsung and MITRE have not published the input, interface, or faulty operation within Timaservice that causes the panic. Network access without authentication or user interaction is sufficient, and successful exploitation crashes the device kernel.
Summary
What happened
Improper input validation in Samsung mobile devices running Android 7.0 allows remote attackers to trigger a kernel panic in Timaservice. Samsung and MITRE have not published the input, interface, or faulty operation within Timaservice that causes the panic. Network access without authentication or user interaction is sufficient, and successful exploitation crashes the device kernel.
The record
- CVE
- CVE-2017-18674
- Published
- Apr 7, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1642
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 7, 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.
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