CVE-2019-15417
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 Spark Pro Android device with a build fingerprint of TECNO/H3722/TECNO-K8:7.0/NRD90M/K8-H3722ABCDE-N-171229V96:user/release-keys contains a pre-installed app with a package name of com.lovelyfont.defcontainer app (versionCode=7, versionName=7.0.5) that allows unauthorized dynamic code loading 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 confidenceThe Tecno Spark Pro Android device contains a pre-installed app (com.lovelyfont.defcontainer v7.0.5) vulnerable to a confused deputy attack that allows any co-located app to perform unauthorized dynamic code loading. This exploits the privileged pre-installed app's ability to load code without proper authorization checks.
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.
-
Verify device model is Tecno Spark ProGo to Settings > About Phone > Model Number (or Device Name) and confirm it reads 'Tecno Spark Pro' or 'Spark Pro'Affected if The device model is NOT Tecno Spark Pro (not affected); if it IS Tecno Spark Pro, proceed to next check
-
Check if vulnerable app package existsUse a file explorer or adb command 'pm list packages | grep lovelyfont' to verify the package com.lovelyfont.defcontainer is installed on the deviceAffected if The package com.lovelyfont.defcontainer is NOT found (not affected); if found, proceed to next check
-
Verify app version is v7.0.5Go to Settings > Apps > LovelyFont DefContainer (or com.lovelyfont.defcontainer) > App info and check the version; alternatively use adb command 'dumpsys package com.lovelyfont.defcontainer | grep versionName'Affected if The installed version is NOT 7.0.5 (may not be affected); if version is 7.0.5, the device is affected
A Tecno Spark Pro device with com.lovelyfont.defcontainer version 7.0.5 installed is vulnerable to CVE-2019-15417 and affected by this confused deputy attack vulnerability.
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 is a firmware-level vulnerability requiring a manufacturer-provided security patch to remove or fix the vulnerable pre-installed app. Users cannot practically remediate this independently.
- 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-15417 — 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-15417 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