CVE-2019-15391
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 4 Selfie Android device with a build fingerprint of asus/WW_Phone/ASUS_X00LD_1:8.1.0/OPM1.171019.011/15.0400.1809.405-0:user/release-keys contains a pre-installed app with a package name of com.log.logservice app (versionCode=1, versionName=1) that allows any app co-located on the device to modify a system property through an exported interface without proper authorization.
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 confidenceThe Asus ZenFone 4 Selfie contains a pre-installed app (com.log.logservice) with an exported interface that allows any co-located app to modify system properties without authorization. This authorization bypass in a system-level app enables privilege escalation, potentially allowing malicious apps to alter system configuration or conduct further exploitation.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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 if the device is an Asus ZenFone 4 Selfie by going to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shellAffected if The device model is Asus ZenFone 4 Selfie (ZE554KL or related variants)
-
Check for vulnerable app presenceVerify the com.log.logservice app is installed by running 'pm list packages | grep logservice' via ADB shell, or check in Settings > Apps > Show system apps for 'logservice'Affected if The package com.log.logservice is present on the device
-
Verify exported componentAnalyze the app's AndroidManifest.xml using 'dumpsys package com.log.logservice' via ADB shell to check for exported receivers or services, or use APK analysis tools to decompile and inspect the manifestAffected if The app declares exported components (receiver/service) that can be invoked by other applications
-
Confirm the authorization bypassAttempt to send a test broadcast or intent to the component using 'adb shell am broadcast -a <component-action>' or 'adb shell am startservice' to verify if the interface accepts commands without permission checksAffected if The exported component accepts and processes intents from any app without requiring system permissions
A user is affected if they own an Asus ZenFone 4 Selfie device with the com.log.logservice app present and its exported components are accessible without authorization.
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 dataEnd users cannot directly remediate this vulnerability; they should await an official firmware/security patch from Asus. As a defensive measure, users should avoid sideloading apps from untrusted sources and ensure Google Play Protect is enabled.
- Consultation4.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 $2,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15391 — 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-15391 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