dbcve.org
Zenfone 3s Max FirmwareOperating system · Asus

CVE-2019-15403

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 3s Max Android device with a build fingerprint of asus/IN_X00G/ASUS_X00G_1:7.0/NRD90M/IN_X00G-14.02.1807.33-20180706: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 3s Max contains a pre-installed system app (com.asus.loguploaderproxy, version 7.0.0.4_170901) with an exposed component that allows other pre-installed apps holding signatureOrSystem permissions to execute arbitrary commands on the device. This represents a privilege escalation vulnerability where malicious or compromised pre-installed apps can leverage this component to gain additional system capabilities.

MitigationSince this is a pre-installed system app vulnerability specific to the ZenFone 3s Max, the primary mitigation is obtaining and applying the vendor firmware update from Asus. Enterprises should inventory affected devices, apply available security patches, and consider network isolation or device replacement 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 3s Max 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 the device model number in Settings > About Phone or run: `getprop ro.product.model`
    Affected if Device model is not Asus ZenFone 3s Max (model ZC520TL or related variants)
  2. Locate the vulnerable app package
    List installed packages and search for com.asus.loguploaderproxy: `pm list packages | grep asus.loguploaderproxy` or check /data/data/ or /system/preinstall/ directories
    Affected if The package com.asus.loguploaderproxy is present on the device
  3. Check app version
    Get the version of the loguploaderproxy app: `dumpsys package com.asus.loguploaderproxy | grep versionName`
    Affected if Version is 7.0.0.4_170901 or any version of this app on the ZenFone 3s Max (all versions are affected)
  4. Verify exposed component
    Analyze the app manifest (AndroidManifest.xml inside the APK) to check for exported components (activities, services, broadcast receivers) that accept signatureOrSystem permissions or are incorrectly exported
    Affected if The app exposes components with signatureOrSystem permission protection that can be invoked by other pre-installed apps
  5. Identify signatureOrSystem privilege holders
    Enumerate all apps holding signatureOrSystem permissions: `pm list packages -s` combined with permission analysis, or check which pre-installed apps have elevated privileges
    Affected if Other pre-installed apps exist with signatureOrSystem permissions that could invoke the vulnerable component

A user is affected if they own an Asus ZenFone 3s Max device that has the com.asus.loguploaderproxy system app installed, as all firmware versions of this model contain the vulnerable pre-installed app with an exposed component callable by other privileged pre-installed apps.

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 specific to the ZenFone 3s Max, the primary mitigation is obtaining and applying the vendor firmware update from Asus. Enterprises should inventory affected devices, apply available security patches, and consider network isolation or device replacement if no update is available.

Fix this in Zenfone 3s Max 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-15403 — 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-15403 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