dbcve.org
Galaxy J7 Prime FirmwareOperating system · Samsung

CVE-2019-15463

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 j7popeltemtr Android device with a build fingerprint of samsung/j7popeltemtr/j7popeltemtr:8.1.0/M1AJQ/J727T1UVS5BSC2: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 j7popeltemtr Android device contains a pre-installed themecenter app (com.samsung.android.themecenter v7.0.1.0) with an exposed component that allows app installation. This capability is accessible to other pre-installed apps holding signatureOrSystem permissions, enabling unauthorized app installation by any pre-installed malicious app.

MitigationSamsung must release a firmware/security patch that removes or properly secures the exposed app installation component in the themecenter app, restricting access to only authorized system components.

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
Galaxy J7 Prime 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. Identify device model
    Go to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell, to confirm the device is Samsung Galaxy J7 Prime
    Affected if Device model is Samsung Galaxy J7 Prime (SM-G610x)
  2. Check if themecenter app is installed
    Run 'pm list packages | grep themecenter' via ADB shell, or inspect the app list in Settings > Apps for 'com.samsung.android.themecenter'
    Affected if Package com.samsung.android.themecenter is present on the device
  3. Verify themecenter app version
    Run 'dumpsys package com.samsung.android.themecenter | grep versionName' via ADB shell to retrieve the installed version
    Affected if Version is 7.0.1.0 or if version cannot be determined on an affected J7 Prime device
  4. Check for vulnerable exposed component
    Use 'dumpsys package com.samsung.android.themecenter' and look for exported activities/services with permission 'signatureOrSystem' in the component declaration, or use an app like Package Manager to inspect exported components
    Affected if The themecenter app exports an app installation component (activity or service) that is accessible to apps with signatureOrSystem permission
  5. Identify pre-installed apps with signatureOrSystem permission
    Run 'pm list permissions -g | grep signatureOrSystem' and cross-reference with pre-installed apps in /system/app or /system/priv-app, or use 'dumpsys package <pkg>' for suspicious pre-installed apps to check their declared permissions
    Affected if There are pre-installed apps (not from Samsung official ROM) holding signatureOrSystem permission that could invoke the exposed themecenter installation component

A Samsung Galaxy J7 Prime device with com.samsung.android.themecenter version 7.0.1.0 that has an exported app installation component accessible to signatureOrSystem apps is affected by this vulnerability.

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

Samsung must release a firmware/security patch that removes or properly secures the exposed app installation component in the themecenter app, restricting access to only authorized system components.

Fix this in Galaxy J7 Prime Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing24.0 h
  • Review / QA16.0 h
88.0 hours of engineering $15,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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