CVE-2019-15419
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 ASUS_X015_1 Android device with a build fingerprint of asus/CN_X015/ASUS_X015_1:7.0/NRD90M/CN_X015-14.00.1709.35-20171215:user/release-keys contains a pre-installed app with a package name of com.lovelyfont.defcontainer app (versionCode=5, versionName=5.0.1) that allows unauthorized command execution via a confused deputy attack. This capability can be accessed by any app co-located on the device.
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 confidenceA pre-installed font-related application (com.lovelyfont.defcontainer, version 5.0.1) on the Asus ASUS_X015_1 Android device contains a confused deputy vulnerability that allows any co-located app to execute commands with elevated privileges. The app exposes a protected capability intended for system use but accessible to all apps on the device, enabling unauthorized command execution.
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.
-
Identify device modelCheck the device model in Settings > About Phone or run 'getprop ro.product.model' via ADBAffected if Device model is Asus X105d or ASUS_X015_1
-
Verify vulnerable app is presentCheck for the package com.loovyfont.defcontainer in installed apps list using ADB command: 'pm list packages | grep lovelyfont' or via Settings > AppsAffected if Package com.lovelyfont.defcontainer is installed on the device
-
Confirm app versionRun 'dumpsys package com.lovelyfont.defcontainer' via ADB to retrieve the installed version, or view it in App Info screenAffected if Version is 5.0.1 or if the app exists regardless of version on affected firmware
-
Check for exposed capabilityRun 'dumpsys package com.lovelyfont.defcontainer' and inspect the exported components (services, receivers, providers) in the outputAffected if The app exports components that are accessible to other apps (exported=true in manifest)
-
Verify app has elevated privilegesReview the app's declared permissions via 'dumpsys package com.lovelyfont.defcontainer' - look for system-level or signature permissionsAffected if The app declares permissions beyond what a normal user app would have
User is affected if they are using an Asus X105d or ASUS_X015_1 device with the com.lovelyfont.defcontainer app installed, as the exposed protected capability allows any app to execute privileged commands.
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 dataThis vulnerability requires a firmware update from Asus to patch or remove the vulnerable pre-installed application; users should not install apps from untrusted sources and should check for available system updates.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15419 — 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-15419 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