dbcve.org
On 7 FirmwareOperating system · Samsung

CVE-2019-15441

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 Samsung on7xeltelgt Android device with a build fingerprint of samsung/on7xeltelgt/on7xeltelgt:8.1.0/M1AJQ/G610LKLU2CSB1:user/release-keys contains a pre-installed app with a package name of com.samsung.android.themecenter app (versionCode=7000100, versionName=7.0.1.0) that allows other pre-installed apps to perform app installation via an accessible app component. This capability can be accessed by any pre-installed app on the device which can obtain signatureOrSystem permissions that are required by other other pre-installed apps that exported their capabilities to other pre-installed app.

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

The Samsung themecenter app (com.samsung.android.themecenter v7.0.1.0) on the on7xeltelgt device contains an exported component that allows other pre-installed apps to perform app installation without proper authorization. Any pre-installed app with signatureOrSystem permissions can exploit this accessible component to install additional apps, creating an elevation of privilege vulnerability.

MitigationSince this is a pre-installed OEM system app, users should ensure the device receives manufacturer security updates. Enterprise security teams may need to consider device replacement or network-level controls as this specific model may no longer receive 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
On 7 FirmwareOperating system
Affected:all versions

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. Confirm device model is Samsung On7
    Check device model number in Settings > About Phone > Model Number. Look for 'on7xeltelgt' or variants of the Samsung On7 device.
    Affected if Device model is on7xeltelgt or other Samsung On7 variants running the themecenter app.
  2. Verify themecenter app is installed
    Navigate to Settings > Apps > Show system apps, then search for 'themecenter' or locate 'com.samsung.android.themecenter' in the app list.
    Affected if The com.samsung.android.themecenter app is present on the device.
  3. Check themecenter app version
    In Settings > Apps > themecenter > App info, note the version number displayed. Compare against v7.0.1.0 mentioned in the CVE.
    Affected if themecenter version is 7.0.1.0 or any version on the Samsung On7 firmware.
  4. Verify exported component exists
    Use a tool like 'adb shell dumpsys package com.samsung.android.themecenter' to examine the app's manifest components. Look for exported Activity, Service, or Receiver entries that handle app installation.
    Affected if The app contains exported components that handle package installation operations.
  5. Check for pre-installed apps with elevated permissions
    Review installed apps in Settings > Apps and identify pre-installed apps holding signatureOrSystem permissions. These can be confirmed via 'adb shell dumpsys package <package> | grep permission'.
    Affected if Pre-installed apps with signatureOrSystem permissions exist on the device, as these are required to exploit the vulnerability.

A user is affected if they are running a Samsung On7 (on7xeltelgt) device with the themecenter app installed and any pre-installed apps with signatureOrSystem permissions are present on the device.

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

Since this is a pre-installed OEM system app, users should ensure the device receives manufacturer security updates. Enterprise security teams may need to consider device replacement or network-level controls as this specific model may no longer receive patches.

Fix this in On 7 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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