dbcve.org
Zenfone 3s Max FirmwareOperating system · Asus

CVE-2019-15395

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=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 · high confidence

The Asus ZenFone 3s Max device contains a pre-installed app (com.asus.loguploaderproxy) with an exported component that allows command execution. This component is accessible to other pre-installed apps holding signatureOrSystem permissions, enabling arbitrary command execution in the context of the vulnerable app.

MitigationApply firmware updates from Asus that address this vulnerability. If unavailable, consider device replacement, as pre-installed system apps cannot be removed or patched by end users.

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 if the device is an Asus ZenFone 3s Max by looking at device settings under Settings > About Phone > Model Number, or by running 'getprop ro.product.model' via ADB
    Affected if The device model shows anything other than ZenFone 3s Max (model number X00ID or Z01HD) - if not this specific model, the device is not affected by this CVE
  2. Verify vulnerable app is installed
    Check for the presence of the package com.asus.loguploaderproxy using ADB command: 'pm list packages | grep asus.loguploaderproxy' or by checking /data/data/ directory
    Affected if The package com.asus.loguploaderproxy exists on the device - its presence indicates the vulnerable component is installed
  3. Check for exported component
    Use 'dumpsys package com.asus.loguploaderproxy' via ADB to inspect the app manifest and look for exported activities, services, or receivers
    Affected if Any activity, service, or receiver with android:exported="true" is found in the package - this indicates the attack surface exists
  4. Verify signatureOrSystem permission requirement
    Review the component permissions using 'aapt dump badging' on the APK or examine the manifest for permission declarations - specifically check if the component requires signatureOrSystem level permissions
    Affected if The exported component requires android.permission.INTERACT_ACROSS_USERS_FULL or similar signatureOrSystem permissions, which allows other pre-installed apps to trigger the command execution

A device is affected only if it is specifically an Asus ZenFone 3s Max (model X00ID/Z01HD) running any firmware version and the com.asus.loguploaderproxy app with its exported vulnerable component is present.

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 firmware updates from Asus that address this vulnerability. If unavailable, consider device replacement, as pre-installed system apps cannot be removed or patched by end users.

Fix this in Zenfone 3s Max Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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