dbcve.org
Samsung PayApplication · Samsung

CVE-2022-36872

MEDIUM · 6.5 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to 5.0.63 / 5.1.47 or later.
See remediation →
67/100
Remediation priority · Elevated
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
Pending Intent hijacking vulnerability in SpayNotification in Samsung Pay prior to version 5.0.63 for KR and 5.1.47 for Global allows attackers to access files without permission via implicit Intent.

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

A Pending Intent hijacking vulnerability exists in Samsung Pay's SpayNotification component. When creating PendingIntents without proper immutability flags, a malicious app can intercept the implicit Intent and gain unauthorized access to files on the device, bypassing Android's permission model.

MitigationUpdate Samsung Pay to version 5.0.63 (Korea) or 5.1.47 (Global) or later. The patched versions include proper FLAG_IMMUTABLE flags when creating PendingIntents to prevent hijacking.

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
Samsung PayApplication
Affected:< 5.1.47
Samsung Pay KrApplication
Affected:< 5.0.63

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

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. Verify Samsung Pay is installed
    Check your device for the Samsung Pay app. On Android, you can run: `adb shell pm list packages | grep samsung.pay` or look for the app in your app drawer.
    Affected if The package com.samsung.android.spay or com.samsung.android.spay Korea is present on the device.
  2. Identify the Samsung Pay variant
    Determine if you have the Korea (Kr) or Global version. Run: `adb shell pm package-info --a com.samsung.android.spay` for Global or `adb shell pm package-info --a com.samsung.android.spay.kr` for Korea. The package name differs between regions.
    Affected if The package name matches either com.samsung.android.spay (Global) or com.samsung.android.spay.kr (Korea).
  3. Check the installed Samsung Pay version
    Run: `adb shell dumpsys package com.samsung.android.spay` (Global) or `adb shell dumpsys package com.samsung.android.spay.kr` (Korea). Look for the versionName field in the output, or check via the app store listing.
    Affected if A version number is returned that you can compare against the affected thresholds.
  4. Compare version against affected ranges
    Review the versionName found in the previous step. For Global (com.samsung.android.spay), compare to 5.1.47. For Korea (com.samsung.android.spay.kr), compare to 5.0.63.
    Affected if The installed version is below 5.1.47 for Global, or below 5.0.63 for Korea.

You are affected if Samsung Pay is installed and the installed version is below 5.1.47 (Global) or below 5.0.63 (Korea), as only those versions contain the vulnerable SpayNotification component with improperly secured PendingIntents.

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.

dbcve · scoped
Upgrade available Upgrade to 5.0.63 / 5.1.47 or later
Fixed in 5.0.635.1.47
Interim mitigation

Update Samsung Pay to version 5.0.63 (Korea) or 5.1.47 (Global) or later. The patched versions include proper FLAG_IMMUTABLE flags when creating PendingIntents to prevent hijacking.

Recommended fix High confidence

Samsung Pay Global: 5.1.47 | Samsung Pay Kr: 5.0.63

  1. Open the Google Play Store or Samsung Galaxy Store on your device
  2. Search for Samsung Pay and check your current installed version
  3. Update Samsung Pay to version 5.1.47 or higher (for Global region)
  4. If using Samsung Pay in Korea (Kr), update to version 5.0.63 or higher
  5. Verify the update was successful by checking the app version in Settings > Apps > Samsung Pay

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Samsung Pay Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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