dbcve.org
Customization ServiceApplication · Samsung

CVE-2021-25373

HIGH · 7.8 CVSS v3.1 Published 2021-04-09
Fix available
A fix is available. Upgrade to 2.2.02.1 / 2.4.03.0 or later.
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
Using unsafe PendingIntent in Customization Service prior to version 2.2.02.1 in Android O(8.x), 2.4.03.0 in Android P(9.0), 2.7.02.1 in Android Q(10.0) and 2.9.01.1 in Android R(11.0) allows local attackers to perform unauthorized action without permission via hijacking the PendingIntent.

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 Customization Service in Android uses an unsafe PendingIntent that lacks proper mutability flags or uses implicit intents, allowing a local malicious application to hijack the PendingIntent and perform unauthorized actions with the privileges of the vulnerable app.

MitigationUpdate the Customization Service to version 2.2.02.1 or higher for Android 8.x, 2.4.03.0 or higher for Android 9.0, 2.7.02.1 or higher for Android 10.0, and 2.9.01.1 or higher for Android 11.0. The fix requires using FLAG_IMMUTABLE when creating PendingIntents and ensuring explicit intents are used.

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
Customization ServiceApplication
Affected:< 2.2.02.1< 2.4.03.0< 2.7.02.1< 2.9.01.1

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 if Customization Service is installed
    On the Android device, go to Settings > Apps > Find 'Customization Service' or 'com.samsung.android.app.cmt' in the app list. Alternatively, use ADB: adb shell pm list packages | grep -i customization
    Affected if The package com.samsung.android.app.cmt is present on the device
  2. Determine the installed version of Customization Service
    In Settings > Apps > Customization Service > App info, note the version number shown (e.g., 2.1.05.3). Or use ADB: adb shell dumpsys package com.samsung.android.app.cmt | grep versionName
    Affected if A version number is returned showing the installed version
  3. Match Android OS version to affected version range
    Check the Android OS version: Settings > About Phone > Android version. Then compare: Android 8.x requires >= 2.2.02.1, Android 9.0 requires >= 2.4.03.0, Android 10.0 requires >= 2.7.02.1, Android 11.0 requires >= 2.9.01.1
    Affected if The installed Customization Service version is below the threshold for your Android version (e.g., below 2.2.02.1 on Android 8.x, below 2.4.03.0 on Android 9.0, below 2.7.02.1 on Android 10.0, or below 2.9.01.1 on Android 11.0)
  4. Confirm the vulnerability condition
    No direct runtime check exists for unsafe PendingIntent in installed APKs. The vulnerability exists if the Customization Service version falls into any of the affected ranges: < 2.2.02.1 OR < 2.4.03.0 OR < 2.7.02.1 OR < 2.9.01.1
    Affected if The installed version is in any of the affected ranges listed

You are affected if Samsung Customization Service is installed and its version is below 2.2.02.1 (Android 8.x), 2.4.03.0 (Android 9.0), 2.7.02.1 (Android 10.0), or 2.9.01.1 (Android 11.0) respectively.

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
Upgrade available Upgrade to 2.2.02.1 / 2.4.03.0 / 2.7.02.1 or later
Fixed in 2.2.02.12.4.03.02.7.02.1
Interim mitigation

Update the Customization Service to version 2.2.02.1 or higher for Android 8.x, 2.4.03.0 or higher for Android 9.0, 2.7.02.1 or higher for Android 10.0, and 2.9.01.1 or higher for Android 11.0. The fix requires using FLAG_IMMUTABLE when creating PendingIntents and ensuring explicit intents are used.

Fix this in Customization Service Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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