Vulnerabilities · 2016 · Google
CVE-2016-3875
Google Android vulnerability
server/wm/WindowManagerService.java in Android 6.x before 2016-09-01 does not enforce the DISALLOW_SAFE_BOOT setting, which allows physically proximate attackers to bypass intended access restrictions and boot to safe mode via unspecified vectors, aka internal bug 26251884.
Affected products
Android. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Android runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- source.android.com/security/bulletin/2016-09-01.html · Vendor Advisory
- android.googlesource.com/platform/frameworks/base/+/69729fa8b13cadbf3173fe1f389fe4f3b7bd0f · Patch
- www.securityfocus.com/bid/92818
- www.securitytracker.com/id/1036763
- nvd.nist.gov/vuln/detail/CVE-2016-3875
- cve.org/CVERecord?id=CVE-2016-3875
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.