CVE-2019-15347
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 Tecno Camon iClick 2 Android device with a build fingerprint of TECNO/H622/TECNO-ID6:8.1.0/O11019/F-180824V116:user/release-keys contains a pre-installed platform app with a package name of com.lovelyfont.defcontainer (versionCode=7, versionName=7.0.11). This app contains an exported service named com.lovelyfont.manager.FontCoverService that allows any app co-located on the device to supply arbitrary commands via shell script to be executed as the system user that are triggered by writing an attacker-selected message to the logcat log. This app cannot be disabled by the user and the attack can be performed by a zero-permission app. Executing commands as the system user can allow a third-party app to video record the user's screen, factory reset the device, obtain the user's notifications, read the logcat logs, inject events in the Graphical User Interface (GUI), and obtains the user's text messages, and more. Executing commands as the system user can allow a third-party app to factory reset the device, obtain the user's notifications, read the logcat logs, inject events in the GUI, change the default Input Method Editor (IME) (e.g., keyboard) with one contained within the attacking app that contains keylogging functionality, and obtains the user's text messages, and more.
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 confidenceA pre-installed system app (com.lovelyfont.defcontainer v7.0.11) on Tecno Camon iClick 2 devices contains an exported service (FontCoverService) that allows any zero-permission app to execute arbitrary shell commands as the system user by writing messages to logcat. This enables privilege escalation attacks including screen recording, factory reset, notification theft, GUI injection, IME replacement with keyloggers, and SMS exfiltration.
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 if the device is a Tecno Camon iClick 2 by going to Settings > About Phone > Device name or model numberAffected if The device model is Tecno Camon iClick 2 or Camon iClick 2
-
Check for vulnerable app presenceUse ADB or a file explorer app to verify the presence of /data/app/com.lovelyfont.defcontainer/ or check installed system apps for package name com.lovelyfont.defcontainerAffected if The package com.lovelyfont.defcontainer is installed on the device
-
Verify FontCoverService is exportedUse ADB command 'dumpsys package com.lovelyfont.defcontainer' to check if the FontCoverService has android:exported="true" in its service declarationAffected if The FontCoverService component is exported and accessible to other apps
-
Confirm app versionCheck the app version of com.lovelyfont.defcontainer via ADB 'dumpsys package com.lovelyfont.defcontainer' or in Settings > Apps > FontCover/defcontainerAffected if The installed version is 7.0.11 or matches the vulnerable build
-
Test command execution capabilityUsing a separate app with no special permissions, attempt to send a message to logcat that would trigger FontCoverService to execute a test command (e.g., 'logcat -d | grep' for a known test string)Affected if Arbitrary shell commands can be executed through the service without any app permissions
A user is affected if they are using a Tecno Camon iClick 2 device with the com.lovelyfont.defcontainer app installed and the FontCoverService is exported, enabling any app to execute system-level 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 the device manufacturer (Tecno) to patch or remove the vulnerable pre-installed app. Users should monitor for OEM security patches and avoid storing sensitive data on affected devices until patched.
- Consultation4.0 h
- Implementation2.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 $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15347 — 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-15347 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