dbcve.org
Zenfone 4 Selfie FirmwareOperating system · Asus

CVE-2019-15398

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 ZenFone 4 Selfie Android device with a build fingerprint of asus/WW_Z01M/ASUS_Z01M_1:7.1.1/NMF26F/WW_user_11.40.208.77_20170922:user/release-keys contains a pre-installed app with a package name of com.asus.loguploaderproxy app (versionCode=1570000015, versionName=7.0.0.3_161222) 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 · moderate confidence

A pre-installed system app (com.asus.loguploaderproxy version 7.0.0.3) on the Asus ZenFone 4 Selfie exposes an accessible exported component that allows arbitrary command execution. Any pre-installed app holding signatureOrSystem permissions can invoke this component to execute commands with elevated system privileges, enabling privilege escalation across pre-installed apps.

MitigationApply the vendor firmware update from Asus that patches this vulnerability, or remove/disable the com.asus.loguploaderproxy app through root-level access if no update is available.

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
    Check if the device is an Asus ZenFone 4 Selfie by going to Settings > About Phone > Model or by running 'getprop ro.product.model' in ADB shell
    Affected if The device model matches ZenFone 4 Selfie (with model numbers like ZD553KL or similar variants)
  2. Verify com.asus.loguploaderproxy is installed
    Run 'pm list packages | grep asus.loguploaderproxy' in ADB shell or check in Settings > Apps for 'LogUploader' or similar Asus system app
    Affected if The package com.asus.loguploaderproxy is present on the device
  3. Check app version
    Run 'dumpsys package com.asus.loguploaderproxy | grep versionName' in ADB shell to retrieve the installed version number
    Affected if The version is 7.0.0.3 or matches the pre-installed version on the ZenFone 4 Selfie firmware
  4. Verify exported component exists
    Run 'dumpsys package com.asus.loguploaderproxy' in ADB shell and look for exported activities/services/receivers, or use an app like Package Manager to inspect the app's manifest
    Affected if The app contains exported components (activities, services, or receivers) that are accessible to other apps
  5. Confirm signatureOrSystem permission apps exist
    Run 'dumpsys package' and look for other pre-installed apps with the signatureOrSystem permission level, or check for apps with elevated privileges using 'pm list permissions -g'
    Affected if There are pre-installed apps with signatureOrSystem permissions that could potentially invoke the vulnerable component

The device is affected if it is an Asus ZenFone 4 Selfie with com.asus.loguploaderproxy installed and an exported component accessible to signatureOrSystem apps, which is the case for all firmware versions of this model.

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

Apply the vendor firmware update from Asus that patches this vulnerability, or remove/disable the com.asus.loguploaderproxy app through root-level access if no update is available.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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