dbcve.org
Zenfone Ar FirmwareOperating system · Asus

CVE-2019-15414

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 AR Android device with a build fingerprint of asus/WW_ASUS_A002/ASUS_A002:7.0/NRD90M/14.1600.1805.51-20180626:user/release-keys contains a pre-installed app with a package name of com.asus.splendidcommandagent app (versionCode=1510200105, versionName=1.2.0.21_180605) 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

The Asus ZenFone AR device contains a pre-installed app (com.asus.splendidcommandagent, v1.2.0.21) with an exported component that allows command execution. This component is accessible to any pre-installed app holding signatureOrSystem permissions, enabling unauthorized privilege escalation and arbitrary command execution within the context of the privileged app.

MitigationThis vulnerability requires an OEM firmware update from Asus to patch or remove the vulnerable pre-installed app. Users should monitor for security updates from the device manufacturer and consider workarounds such as minimizing use of the affected device until a patch 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 Ar 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. Verify device model is Asus ZenFone AR
    Check the device model in Settings > About Phone, or run 'getprop ro.product.model' via ADB shell
    Affected if Device model is not Asus ZenFone AR (other models are not affected by this specific CVE)
  2. Check if vulnerable app is installed
    Run 'pm list packages | grep splendidcommandagent' or 'pm list packages com.asus.splendidcommandagent' via ADB shell
    Affected if The package com.asus.splendidcommandagent is present on the device
  3. Inspect exported components in the vulnerable app
    Run 'dumpsys package com.asus.splendidcommandagent' via ADB shell and look for exported activities/services with intent-filter declarations
    Affected if The app contains exported components (activities or services) that accept external intents
  4. Check for pre-installed apps with signatureOrSystem permissions
    Run 'dumpsys package | grep -A5 "android.permission.SIGNATURE_OR_SYSTEM"' via ADB shell to list apps holding elevated permissions
    Affected if Other pre-installed apps with signatureOrSystem permissions exist (these could exploit the vulnerable component)
  5. Verify OEM firmware update status
    Check Settings > System > Software Update, or run 'getprop ro.build.version.security_patch' via ADB shell to check the last security patch level
    Affected if No OEM security update has been applied to remove or patch the vulnerable app

The device is affected if it is an Asus ZenFone AR running firmware with the com.asus.splendidcommandagent (v1.2.0.21) app installed and no OEM security update has patched or removed this vulnerable pre-installed component.

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

This vulnerability requires an OEM firmware update from Asus to patch or remove the vulnerable pre-installed app. Users should monitor for security updates from the device manufacturer and consider workarounds such as minimizing use of the affected device until a patch is available.

Fix this in Zenfone Ar Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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