Memory corruption via WifiService adb-cmd
Published Apr 7, 2020 · Updated Aug 5, 2024
NULL pointer dereference in Samsung Android M(6.0) WifiService allows remote attackers to corrupt memory via an adb-cmd request. WifiService processes the adb-cmd input and dereferences a NULL pointer, corrupting memory instead of handling the invalid state safely. Exploitation requires access to the device's ADB command interface; observed impact is service instability or memory corruption, with no public evidence of code execution.
Summary
What happened
NULL pointer dereference in Samsung Android M(6.0) WifiService allows remote attackers to corrupt memory via an adb-cmd request. WifiService processes the adb-cmd input and dereferences a NULL pointer, corrupting memory instead of handling the invalid state safely. Exploitation requires access to the device's ADB command interface; observed impact is service instability or memory corruption, with no public evidence of code execution.
The record
- CVE
- CVE-2017-18665
- Published
- Apr 7, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1210
- Attack vector
- adjacent
- 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