Wi-Fi interface takeover via missing D-Bus policy
Published Jan 22, 2020 · Updated Aug 5, 2024
Improper privilege management in Samsung Galaxy Gear firmware before build RE2 allows local users to control the Wi-Fi interface. The wpa_supplicant system service lacks a D-Bus security policy, so it accepts privileged Wi-Fi control requests from any unprivileged process. Process execution on the watch is required; exploitation can change Wi-Fi behavior through the service but does not itself grant root code execution.
Summary
What happened
Improper privilege management in Samsung Galaxy Gear firmware before build RE2 allows local users to control the Wi-Fi interface. The wpa_supplicant system service lacks a D-Bus security policy, so it accepts privileged Wi-Fi control requests from any unprivileged process. Process execution on the watch is required; exploitation can change Wi-Fi behavior through the service but does not itself grant root code execution.
The record
- CVE
- CVE-2018-16272
- Published
- Jan 22, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1068
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 22, 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
- Your Watch Can Watch Youproof 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