dbcve.org
Galaxy S7 Edge FirmwareOperating system · Samsung

CVE-2019-15447

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 S7 Edge Android device with a build fingerprint of samsung/hero2ltexx/hero2lte:8.0.0/R16NW/G935FXXS4ESC3:user/release-keys contains a pre-installed app with a package name of com.samsung.android.themecenter app (versionCode=7000000, versionName=7.0.0.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 · moderate confidence

The Samsung S7 Edge themecenter app (com.samsung.android.themecenter) exports a component that allows app installation without proper permission validation. Any pre-installed app holding signatureOrSystem permissions can invoke this component to install additional apps, enabling privilege escalation among pre-installed system apps.

MitigationApply vendor firmware update from Samsung addressing CVE-2019-15447; if unavailable, consider network-level controls to restrict app installation traffic from affected device.

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 S7 Edge 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 Galaxy S7 Edge
    Check device model number in Settings > About Phone > Model Number. The affected model is SM-G935x (where x varies by carrier region).
    Affected if Device model number starts with SM-G935 and runs Samsung firmware
  2. Verify themecenter app is installed
    Check for com.samsung.android.themecenter in Android Settings > Apps > All Apps, or use adb command: pm list packages | grep themecenter
    Affected if The themecenter package com.samsung.android.themecenter is present on the device
  3. Check for apps with signatureOrSystem permissions
    Use adb: adb shell pm list permissions -g | grep signatureOrSystem. Review output for pre-installed apps holding this elevated permission level.
    Affected if Any pre-installed app with signatureOrSystem permission is present on the device (this permission allows exploitation of the vulnerable component)
  4. Verify exported component exists in themecenter
    Use adb: adb shell dumpsys package com.samsung.android.themecenter | grep -A5 "android:exported". Look for an activity or service with export flag set to true related to app installation.
    Affected if The themecenter app exports an activity or service that handles app installation (visible in package manifest)
  5. Confirm firmware version is unpatched
    Check Android security patch level in Settings > About Phone > Security patch level. CVE-2019-15447 was addressed in Samsung security patches released after November 2019.
    Affected if Security patch level is November 2019 or earlier, or if the specific S7 Edge firmware version predates the CVE fix

A Samsung Galaxy S7 Edge (SM-G935x) with the com.samsung.android.themecenter app installed and any signatureOrSystem privileged app present is affected if the firmware security patch level predates the November 2019 Samsung security update.

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

Apply vendor firmware update from Samsung addressing CVE-2019-15447; if unavailable, consider network-level controls to restrict app installation traffic from affected device.

Fix this in Galaxy S7 Edge Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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