Kernel module signature bypass via count tampering
Published Apr 7, 2020 · Updated Aug 5, 2024
Signature bypass in Samsung mobile software on Android 6.0 and 7.0 allows remote attackers to evade kernel module verification via a modified count. The kernel module verifier uses a changeable module-count value when deciding whether a ko file has a valid signature, so count tampering defeats the integrity check. Exploitation applies only to affected Exynos5433, Exynos7420, or Exynos7870 devices and permits an unauthorized kernel module to pass verification; public records do not disclose the delivery path.
Summary
What happened
Signature bypass in Samsung mobile software on Android 6.0 and 7.0 allows remote attackers to evade kernel module verification via a modified count. The kernel module verifier uses a changeable module-count value when deciding whether a ko file has a valid signature, so count tampering defeats the integrity check. Exploitation applies only to affected Exynos5433, Exynos7420, or Exynos7870 devices and permits an unauthorized kernel module to pass verification; public records do not disclose the delivery path.
The record
- CVE
- CVE-2017-18689
- Published
- Apr 7, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-354, T1547.006
- 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.
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