dbcve.org
Samsung PayApplication · Samsung

CVE-2022-36871

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 NotiCenterUtils 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 NotiCenterUtils in Samsung Pay. The app improperly uses implicit Intents with Pending Intents, allowing malicious applications to intercept these Intents and gain unauthorized access to files on the device without proper permissions.

MitigationUpdate Samsung Pay to version 5.0.63 (Korea) or 5.1.47 (global) or later. Ensure Pending Intents use explicit Intents and immutable flags.

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 if Samsung Pay app exists on the device via device settings under Apps or by running: adb shell pm list packages | grep samsung.pay
    Affected if Samsung Pay package (com.samsung.android.spay or com.samsung.android.spaykr) is present on the device
  2. Identify the Samsung Pay variant
    Determine if the installed version is the global or Korea variant by checking the package name: adb shell dumpsys package <package_name> | grep -E 'packageName|versionName' (global: com.samsung.android.spay, Korea: com.samsung.android.spaykr)
    Affected if Either variant is installed
  3. Retrieve installed Samsung Pay version
    Run: adb shell dumpsys package <package_name> | grep versionName, or view version in Settings > Apps > Samsung Pay > App info
    Affected if Version number is visible and can be compared
  4. Compare version against affected ranges
    For global Samsung Pay: verify version is less than 5.1.47. For Samsung Pay Kr: verify version is less than 5.0.63
    Affected if Installed version is below 5.1.47 (global) or below 5.0.63 (Korea)
  5. Check if Pending Intent vulnerability is exploitable
    The vulnerability in NotiCenterUtils requires the app to be active and process pending intents. No direct config check available; version-based assessment is the primary indicator
    Affected if Samsung Pay is installed and running with a version below the fixed releases

The environment is affected if Samsung Pay (global version < 5.1.47 or Korea version < 5.0.63) is installed 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.

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. Ensure Pending Intents use explicit Intents and immutable flags.

Recommended fix High confidence

Samsung Pay 5.1.47 (Global) or Samsung Pay 5.0.63 (KR)

  1. Open the Galaxy Store or Google Play Store on your Samsung device
  2. Search for Samsung Pay
  3. Check the current installed version in the app's information page
  4. If version is below 5.1.47 (Global) or 5.0.63 (KR), tap Update to install the latest version
  5. Alternatively, ensure automatic updates are enabled for Samsung Pay in your app store settings
  6. After updating, verify the version number matches the fixed release (5.1.47 Global / 5.0.63 KR)

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

Fix this in Samsung Pay Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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