dbcve.org
P1 FirmwareOperating system · Leagoo

CVE-2018-14999

CRITICAL · 9.1 CVSS v3.0 Published 2019-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Leagoo P1 device with a build fingerprint of sp7731c_1h10_32v4_bird:6.0/MRA58K/android.20170629.214736:user/release-keys contains a pre-installed platform app with a package name of com.wtk.factory (versionCode=1, versionName=1.0) that contains an exported broadcast receiver named com.wtk.factory.MMITestReceiver allows any app co-located on the device to programmatically initiate a factory reset. In addition, the app initiating the factory reset does not require any permissions. A factory reset will remove all user data and apps from the device. This will result in the loss of any data that have not been backed up or synced externally. The capability to perform a factory reset is not directly available to third-party apps (those that the user installs themselves with the exception of enabled Mobile Device Management (MDM) apps), although this capability can be obtained by leveraging an unprotected app component of a pre-installed platform app.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Leagoo P1 device contains a pre-installed platform app (com.wtk.factory v1.0) with an exported broadcast receiver (com.wtk.factory.MMITestReceiver) that allows any application on the device to trigger a factory reset without any permissions. This unprotected component can be invoked by any app to completely wipe all user data and installed applications.

MitigationRemove or disable the exported broadcast receiver in the com.wtk.factory app by setting android:exported='false' or requiring a protected permission; distribute via firmware OTA update. As an interim measure, enterprise environments may deploy MDM policies to detect or restrict devices with this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
P1 FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check if the device is a Leagoo P1 by reviewing the device Settings > About Phone > Model or by running 'getprop ro.product.model' in ADB shell
    Affected if Device model shows as Leagoo P1 or P1
  2. Check for vulnerable app presence
    Run 'pm list packages | grep wtk.factory' in ADB shell or check Settings > Apps for com.wtk.factory
    Affected if The package com.wtk.factory is installed on the device
  3. Verify exported broadcast receiver
    Run 'pm dump com.wtk.factory | grep -A 20 MMITestReceiver' in ADB shell to inspect the receiver configuration
    Affected if The output shows android:exported=true or no android:exported attribute (defaults to true) for the MMITestReceiver component
  4. Confirm receiver action name
    Run 'pm dump com.wtk.factory | grep -B 5 MMITestReceiver' to find the intent filter action (typically android.intent.action.MASTER_CLEAR or similar factory reset intent)
    Affected if An intent-filter action for factory reset is defined and the receiver is exported

The device is affected if it is a Leagoo P1 with the com.wtk.factory app installed and the MMITestReceiver broadcast receiver is exported (android:exported not set to false), allowing any app to trigger a factory reset.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove or disable the exported broadcast receiver in the com.wtk.factory app by setting android:exported='false' or requiring a protected permission; distribute via firmware OTA update. As an interim measure, enterprise environments may deploy MDM policies to detect or restrict devices with this vulnerability.

Fix this in P1 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14999 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14999 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data