CVE-2019-15400
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 · uneditedThe Asus ZenFone 3 Ultra Android device with a build fingerprint of asus/WW_Phone/ASUS_A001:7.0/NRD90M/14.1010.1804.75-20180612: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 confidenceThe Asus ZenFone 3 Ultra contains a pre-installed system app (com.asus.loguploaderproxy) with an exported component that accepts and executes commands. This component is accessible to other pre-installed apps holding signatureOrSystem permissions, allowing local privilege escalation from one pre-installed app to another.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify device modelCheck if the device is an Asus ZenFone 3 Ultra by checking system property 'ro.product.model' via 'getprop ro.product.model' or checking Settings > About Phone > Model numberAffected if Device model is not Asus ZenFone 3 Ultra (this CVE only affects that specific model)
-
Check if vulnerable app is installedUse ADB command 'pm list packages | grep asus.loguploaderproxy' or check for /data/app/ directory containing 'com.asus.loguploaderproxy' to verify the app is present on the deviceAffected if The package com.asus.loguploaderproxy is installed on the device
-
Verify exported component existsUse ADB command 'dumpsys package com.asus.loguploaderproxy' and look for exported activities, services, or receivers in the package manifest information. Alternatively, use 'aapt dump badging' on the APK if accessibleAffected if The app contains exported components (activities, services, or receivers with android:exported="true" or that accept intents without permission)
A user is affected if they are using an Asus ZenFone 3 Ultra device that has the com.asus.loguploaderproxy app installed with an exported component that other pre-installed apps can invoke for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 dataUsers should contact Asus for a firmware/security update to remove or secure this component. Until then, avoid using the device for sensitive operations and consider device replacement if the vendor does not provide a patch.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15400 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15400 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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