dbcve.org
Zenfone 4 Selfie FirmwareOperating system · Asus

CVE-2019-15406

HIGH · 7.8 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 →
80/100
Remediation priority · High
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 Asus ASUS_X00LD_3 Android device with a build fingerprint of asus/WW_Phone/ASUS_X00LD_3:7.1.1/NMF26F/14.0400.1806.203-20180720:user/release-keys contains a pre-installed app with a package name of com.asus.loguploaderproxy app (versionCode=1570000020, versionName=7.0.0.4_170901) that allows other pre-installed apps to perform command execution via an accessible app component. This capability can be accessed by any pre-installed app on the device which can obtain signatureOrSystem permissions that are required by other other pre-installed apps that exported their capabilities to other pre-installed 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 Asus ASUS_X00LD_3 device contains a pre-installed app (com.asus.loguploaderproxy) with an exported component that accepts commands and executes them on the device. This component is protected by signatureOrSystem permissions, meaning only other pre-installed system apps with elevated privileges can invoke it, creating a privilege escalation path within the pre-installed app ecosystem.

MitigationThis vulnerability requires a firmware update from Asus to patch or remove the vulnerable com.asus.loguploaderproxy app. Organizations should consider device replacement or contact Asus for patch availability while implementing compensating controls such as device inventory tracking and MDM policies.

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
Zenfone 4 Selfie 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 and firmware
    Check the device build number and model: Go to Settings > About Phone > Model Number or run 'getprop ro.product.model' and 'getprop ro.build.display.id' via ADB shell
    Affected if Model number is ASUS_X00LD_3 or Zenfone 4 Selfie with any firmware version
  2. Check if vulnerable app is installed
    Run 'pm list packages | grep asus.loguploaderproxy' or 'dumpsys package com.asus.loguploaderproxy' via ADB shell
    Affected if The package com.asus.loguploaderproxy exists on the device
  3. Inspect app manifest for exported components
    Extract the APK from /data/app/ or /system/priv-app/ and examine AndroidManifest.xml, or use 'dumpsys package com.asus.loguploaderproxy' to list components
    Affected if The app has an exported Activity, Service, or Receiver that accepts commands
  4. Verify permission protection level
    Check the manifest permission declarations for the exported component; look for 'android:permission="android.permission.SIGNATURE_OR_SYSTEM"' or similar elevated privilege protection
    Affected if The exported component is protected by signatureOrSystem permissions but accepts arbitrary commands for execution

The device is affected if it is an Asus Zenfone 4 Selfie (ASUS_X00LD_3) with the com.asus.loguploaderproxy app installed and that app contains an exported component protected by signatureOrSystem permissions.

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

This vulnerability requires a firmware update from Asus to patch or remove the vulnerable com.asus.loguploaderproxy app. Organizations should consider device replacement or contact Asus for patch availability while implementing compensating controls such as device inventory tracking and MDM policies.

Fix this in Zenfone 4 Selfie Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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