CVE-2016-3875

Description

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.

Category

6.8
CVSS
Severity: Medium
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.03%
Vendor Advisory android.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
http://www.securityfocus.com/bid/92818 vdb entry
http://source.android.com/security/bulletin/2016-09-01.html vendor advisory
http://www.securitytracker.com/id/1036763 vdb entry
https://android.googlesource.com/platform/frameworks/base/+/69729fa8b13cadbf3173fe1f389fe4f3b7bd0f9c issue tracking patch

Frequently Asked Questions

What is the severity of CVE-2016-3875?
CVE-2016-3875 has been scored as a medium severity vulnerability.
How to fix CVE-2016-3875?
To fix CVE-2016-3875, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2016-3875 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2016-3875 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.