dbcve.org
Zenfone 5q FirmwareOperating system · Asus

CVE-2019-15409

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 5Q Android device with a build fingerprint of asus/WW_Phone/ASUS_X017D_2:7.1.1/NGI77B/14.0400.1809.059-20181016: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 ZenFone 5Q contains a pre-installed app (com.asus.loguploaderproxy) with an exported component that accepts commands from other pre-installed apps holding signatureOrSystem permissions. This allows local privilege escalation within the pre-installed app ecosystem, enabling any privileged pre-installed app to execute arbitrary commands through the vulnerable app's accessible component.

MitigationAsus should release a firmware update that removes the exported component or adds proper permission validation to the com.asus.loguploaderproxy app; users should apply OTA updates when 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 5q 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. Confirm device model is Asus ZenFone 5Q
    Check the device model number in Settings > About Phone or via 'getprop ro.product.model' command over ADB
    Affected if Device model is Asus ZenFone 5Q (local model) and runs any firmware version
  2. Verify com.asus.loguploaderproxy app exists
    List installed packages via 'pm list packages' over ADB or check in Settings > Apps; look for package name 'com.asus.loguploaderproxy'
    Affected if The package com.asus.loguploaderproxy is installed on the device
  3. Check if the app has exported components
    Use 'dumpsys package com.asus.loguploaderproxy' over ADB to inspect the package's components; look for android:exported="true" in the AndroidManifest or check component declarations
    Affected if The vulnerable app declares exported activities, services, or receivers that can be invoked by other privileged apps
  4. Inspect component permission requirements
    Analyze the exported component's android:permission attribute or the component's intent-filter declarations; use 'aapt dump badging /path/to/loguploaderproxy.apk' if APK is extractable
    Affected if The exported component accepts commands without validating that the calling app holds signatureOrSystem permissions, or accepts intents from any privileged pre-installed app

If the device is an Asus ZenFone 5Q with the com.asus.loguploaderproxy app present and that app contains exported components accessible to other pre-installed apps, the environment is affected by this privilege escalation vulnerability.

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

Asus should release a firmware update that removes the exported component or adds proper permission validation to the com.asus.loguploaderproxy app; users should apply OTA updates when available.

Fix this in Zenfone 5q Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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