dbcve.org
Power 5 FirmwareOperating system · Leagoo

CVE-2019-15363

MEDIUM · 5.5 CVSS v3.1 Published 2019-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 Power 5 Android device with a build fingerprint of LEAGOO/Power_5/Power_5:8.1.0/O11019/1532686195:user/release-keys contains a pre-installed app with a package name of com.mediatek.wfo.impl app (versionCode=27, versionName=8.1.0) that allows any app co-located on the device to modify a system property through an exported interface without proper authorization.

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 · moderate confidence

The Leagoo Power 5 Android device ships with a pre-installed MediaTek WiFi Offload (WFO) app (com.mediatek.wfo.impl) that exposes an exported interface allowing any co-located application to modify system properties without proper authorization checks. This represents a local privilege escalation/authorization bypass vulnerability where malicious or compromised apps on the same device can alter system configuration through this unprotected IPC mechanism.

MitigationSince this is a pre-installed system app vulnerability on a specific device model, remediation requires either an OEM firmware update that patches or removes the vulnerable component, or disabling/root-based removal of the app. Users should check for vendor updates and avoid installing applications from untrusted sources.

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
Power 5 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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. Verify device model is Leagoo Power 5
    Check the device model number in Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell
    Affected if The model number is NOT Leagoo Power 5 or variant (such as P5) - if so, this CVE does not apply
  2. Identify if the vulnerable app is installed
    Check for the presence of the package com.mediatek.wfo.impl using 'pm list packages | grep mediatek.wfo' via ADB shell or a file explorer app
    Affected if The package com.mediatek.wfo.impl is NOT found - if so, the device may already be patched or is a different variant
  3. Check if the app has exported components
    Use 'dumpsys package com.mediatek.wfo.impl' via ADB shell and look for 'exported=true' under <activity>, <service>, or <receiver> tags in the AndroidManifest
    Affected if The app components are NOT exported (exported=false or not set) - if so, the vulnerability may not be exploitable in the current configuration
  4. Verify the WFO service is accessible
    Run 'dumpsys package com.mediatek.wfo.impl | grep -A5 service' to list services and check if any service components have android:exported="true"
    Affected if The WFO service or activity interfaces are exported, allowing any app to bind to them - this confirms the vulnerability is present and exploitable

A user is affected if they use a Leagoo Power 5 device with the com.mediatek.wfo.impl app installed and that app has exported service or activity interfaces that accept system property modifications without authentication.

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

Since this is a pre-installed system app vulnerability on a specific device model, remediation requires either an OEM firmware update that patches or removes the vulnerable component, or disabling/root-based removal of the app. Users should check for vendor updates and avoid installing applications from untrusted sources.

Fix this in Power 5 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15363 — 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-2019-15363 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