LiveActive security incident?Get immediate response
CVE Record

CVE-2017-10709: The lockscreen on Elephone P9000 devices (running Android 6.0) allows physically proximate attackers to byp...

The lockscreen on Elephone P9000 devices (running Android 6.0) allows physically proximate attackers to bypass a wrong-PIN lockout feature by pressing backspace after each PIN guess.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-10709 is a lockscreen weakness in Elephone P9000 phones running Android 6.0. A person holding the device could bypass the normal wrong-PIN lockout behavior and keep attempting PINs. This is mainly a lost, stolen, or shared-device risk, not a remote network compromise.

Executive priority

Treat this as a targeted device-retirement and asset-control issue. It is not a broad enterprise emergency, but any affected phone with sensitive data should be removed from use or confirmed patched because physical loss could weaken lockscreen protection.

Technical view

The issue affects the Elephone P9000 lockscreen implementation on Android 6.0. Public CVE text says the wrong-PIN lockout feature can be bypassed through local interaction, enabling repeated PIN attempts by a physically proximate attacker. The source bundle does not provide CVSS, CWE, CPE, patch status, or evidence of active exploitation.

Likely exposure

Exposure appears limited to Elephone P9000 devices running Android 6.0. Organizations are most at risk if these phones remain in managed fleets, field use, testing labs, or contain sensitive local data. The bundle does not identify other Elephone models or broader Android versions as affected.

Exploitation context

This requires physical proximity to the device. Public references include a Trustwave advisory, SpiderLabs blog, Reddit discussion, Security.nl article, and YouTube reference. The CVE is not listed as KEV in the bundle, and no cited source here establishes active exploitation in the wild.

Researcher notes

Evidence is sparse: the CVE description names Elephone P9000 on Android 6.0 and describes a lockout bypass, but no CVSS, CWE, affected CPEs, or fixed versions are provided. Avoid generalizing to other devices without vendor or advisory confirmation.

Mitigation direction

  • Inventory managed Android assets for Elephone P9000 running Android 6.0.
  • Check vendor or Trustwave advisory guidance for any confirmed firmware update.
  • Retire or replace affected devices if no supported fix is available.
  • Use MDM controls for encryption, remote wipe, and strong screen-lock policy.
  • Avoid storing sensitive local data on affected handsets.

Validation and detection

  • Confirm device model and Android version through MDM or asset records.
  • Check whether affected devices are still assigned, shared, stored, or field deployed.
  • Verify firmware support status against vendor or advisory information.
  • Assess lost-device impact based on local data and enrolled account access.
  • Record compensating controls such as encryption and remote wipe coverage.
Prepared
Confidence
medium
Sources
7

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.

cve · low confidence lookup

CVE-2017-10709 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
6Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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