LiveActive security incident?Get immediate response
CVE Record

CVE-2016-6769: An elevation of privilege vulnerability in Smart Lock could enable a local malicious user to access Smart L...

An elevation of privilege vulnerability in Smart Lock could enable a local malicious user to access Smart Lock settings without a PIN. This issue is rated as Moderate because it first requires physical access to an unlocked device where Smart Lock was the last settings pane accessed by the user. Product: Android. Versions: 5.0.2, 5.1.1, 6.0, 6.0.1. Android ID: A-29055171.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2016-6769 is an Android Smart Lock issue. With physical access to an already unlocked device, and only if Smart Lock was the last settings pane opened, a local malicious user could reach Smart Lock settings without entering the PIN. Business risk is limited by those prerequisites, but shared or unattended legacy devices are exposed. Exposure is most likely on legacy Android 5.x and 6.x devices still in use, especially unmanaged, shared, kiosk-adjacent, or BYOD devices where users may leave devices unlocked. Current supported Android versions are not listed as affected in the provided sources. Treat this as a legacy-device hygiene issue, not an internet-scale emergency. Prioritize removal or update of affected Android 5.x and 6.x devices in shared, unmanaged, or sensitive environments where physical access is plausible. Mitigation focus: Update affected Android devices using vendor security guidance for the December 2016 bulletin.; Retire or isolate Android 5.x and 6.x devices where updates are unavailable.; Enforce short screen-lock timeout and user training for unattended devices..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-6769 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Google Inc.AndroidAndroid-5.0.2, Android-5.1.1, Android-6.0, Android-6.0.1Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.