CVE-2018-14999: n/a vulnerability

CVE-2018-14999: The Leagoo P1 device with a build fingerprint of sp7731c_1h10_32v4_bird:6.0/MRA58K/android.20170629.214736:...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 5, 2024, 09:46 UTC (UTC+00:00)

Security readout for executives and security teams

Plain-English summary

CVE-2018-14999 describes a Leagoo P1 firmware flaw where a pre-installed factory testing app can let another app on the same phone trigger a factory reset. The business impact is data loss and operational disruption on affected devices, not remote network compromise based on the provided sources.

Executive priority

Treat this as a targeted mobile fleet risk. Prioritize action if affected Leagoo P1 devices handle business data, shared-user workflows, or field operations where a wipe would interrupt service or destroy unsynced records.

Technical view

The affected Leagoo P1 build includes com.wtk.factory version 1.0 with an exported com.wtk.factory.MMITestReceiver. The CVE states any co-located app can programmatically initiate factory reset without permissions, removing user data and installed apps. No CVSS, CWE, CPE, or vendor fix is provided in the bundle.

Likely exposure

Exposure appears limited to Leagoo P1 devices with the listed Android 6.0 build fingerprint and vulnerable pre-installed platform app. The bundle does not support applying this CVE broadly to all Android devices or other Leagoo models.

Exploitation context

The cited CVE requires a malicious or unwanted app already installed on the affected device. KEV is false, and the provided sources do not cite active exploitation. The main outcome is forced device wipe and loss of unsynced data.

Researcher notes

The source bundle is narrow and incomplete: no CVSS, CWE, CPE, patch reference, or exploitation evidence is provided. The key claim is an unprotected exported receiver in a pre-installed platform app enabling factory reset by a local app.

Mitigation direction

Inventory whether any Leagoo P1 devices with the listed build remain in use.
Check vendor or fleet-management guidance for firmware updates or supported removal options.
Disable or remove the vulnerable pre-installed app only through supported enterprise controls.
Restrict untrusted app installation on affected devices.
Ensure device data is backed up or synced externally.
Replace unsupported affected devices if no reliable remediation exists.

Validation and detection

Confirm device model and build fingerprint against the CVE description.
Review managed-device inventory for the com.wtk.factory package and version 1.0.
Verify whether com.wtk.factory.MMITestReceiver is exported without triggering factory reset.
Check MDM policies for app installation restrictions and backup enforcement.
Document any affected devices and remediation status.

Prepared: Jun 6, 2026, 21:12 UTC (UTC+00:00)
Confidence: medium
Sources: 4

Public sources used

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-2018-14999 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: Apr 25, 2019, 19:35 UTC (UTC+00:00)

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

4Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5
https://www.kryptowire.com/portal/wp-content/uploads/2018/12/DEFCON-26-Johnson-and-Stavrou-Vulnerable-Out-of-the-Box-An-Eval-of-Android-Carrier-Devices-WP-Updated.pdfCVE reference · x_refsource_MISC
https://www.kryptowire.com/portal/android-firmware-defcon-2018/CVE reference · x_refsource_MISC
https://www.kryptowire.com/CVE reference · x_refsource_MISC

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.