Security readout for executives and security teams
Plain-English summary
This is a low-severity physical-access bypass in an Android app-lock product. If a device uses Easyelife App lock 1.9.2 to protect apps, someone holding the unlocked device may bypass the app’s PIN overlay and open protected apps such as Chrome.
Executive priority
Handle as a low-priority hardening issue unless the app protects sensitive data on shared, lost, or easily accessed Android devices. The business concern is misplaced trust in an app overlay rather than remote compromise.
Technical view
The lock is described as an overlay instead of Android secure authentication APIs. The CVE cites exposed navigation routes through advertisement or browser intents as allowing lockscreen verification evasion. Impact is limited to local physical access with low confidentiality impact.
Likely exposure
Exposure appears limited to Android devices running Easyelife App lock, package locker.app.safe.applocker, version 1.9.2, where it is relied on to restrict app access. Enterprise exposure is most likely on BYOD or unmanaged devices.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The attack requires physical access to the Android device. The public description discusses bypass conditions but does not establish broad exploitation or remote risk.
Researcher notes
CWE-288 is authentication bypass by alternate path. CVSS is 2.4 with physical attack vector, low complexity, no privileges, no user interaction, unchanged scope, and low confidentiality impact. Patch status is not stated in the source bundle.
Mitigation direction
- Do not rely on this app as a primary security boundary.
- Use Android device lock, work profile, or MDM controls for sensitive apps.
- Inventory and remove or disable Easyelife App lock 1.9.2 where practical.
- Check vendor, Play Store, or repository guidance for updates or fixes.
- Treat exposed browser sessions as potentially viewable after device loss.
Validation and detection
- Check Android inventory for package locker.app.safe.applocker version 1.9.2.
- Identify devices where this app protects sensitive apps or browser access.
- Confirm whether MDM policy relies on third-party app-lock overlays.
- Review vendor, Play Store, and repository sources for updated guidance.
- Document compensating controls for affected BYOD or unmanaged devices.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege 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 lookupCVE-2025-68710 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N0.91.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
2.4LowVector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://play.google.com/store/apps/details?id=locker.app.safe.applockerCVE reference, mitre
- https://github.com/actuator/locker.app.safe.applockerCVE reference, mitre
- https://github.com/actuator/locker.app.safe.applocker/blob/main/CVE-2025-68710CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.