dbcve.org
Tecno\/h612\/tecno Id5a\Operating system · Tecno Mobile

CVE-2019-15349

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 Tecno Camon Android device with a build fingerprint of TECNO/H612/TECNO-ID5a:8.1.0/O11019/F-180828V106: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.service.FunctionService that allows any app co-located on the device to supply the file path to a Dalvik Executable (DEX) file which it will dynamically load within its own process and execute in with its own system privileges. 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 code as the system user can allow a third-party app to factory reset the device, obtain the user's Wi-Fi passwords, 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 confidence

A pre-installed system app (com.lovelyfont.defcontainer v7.0.11) on Tecno Camon Android devices contains an exported service (FunctionService) that allows any co-located app to supply a DEX file path for dynamic loading and execution with system-level privileges. This zero-permission attack vector cannot be disabled by users and enables arbitrary code execution as the system user.

MitigationThis vulnerability requires a firmware update from Tecno to either remove the vulnerable app/service or implement proper permission checks. Users should monitor for manufacturer security patches.

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
Tecno\/h612\/tecno Id5a\Operating system
Affected:= 8.1.0\/o11019\/f-180828v106\

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 and variant
    Check if the device is Tecno Camon model h612 (tecno Id5a) using 'getprop ro.product.device' or 'getprop ro.product.model'
    Affected if Device model is h612 or tecno Id5a
  2. Confirm Android OS version
    Check Android version using Settings > About Phone or 'getprop ro.build.version.release'
    Affected if Android version is 8.1.0 (build o11019/f-180828v106)
  3. Identify the vulnerable app
    List installed packages and check for 'com.lovelyfont.defcontainer' using 'pm list packages' or a package manager app
    Affected if Package com.lovelyfont.defcontainer is present on the device
  4. Check app version
    Query the app version using 'dumpsys package com.lovelyfont.defcontainer' or view in device app settings
    Affected if Version is 7.0.11
  5. Verify service export status
    Use 'adb shell dumpsys package com.lovelyfont.defcontainer' to inspect the manifest and check if FunctionService has android:exported=true
    Affected if FunctionService is exported (android:exported not set to false)

A device is affected if it is a Tecno Camon h612/Id5a running Android 8.1.0 with com.lovelyfont.defcontainer v7.0.11 installed and its FunctionService remains exported.

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 a firmware update from Tecno to either remove the vulnerable app/service or implement proper permission checks. Users should monitor for manufacturer security patches.

Fix this in Tecno\/h612\/tecno Id5a\ Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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