CVE-2022-36870
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 · uneditedPending Intent hijacking vulnerability in MTransferNotificationManager 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 confidenceThis is a Pending Intent hijacking vulnerability in Samsung Pay's MTransferNotificationManager. The app uses implicit Intents in Pending Intents, allowing malicious apps to intercept and steal the Pending Intent and thereby gain unauthorized access to files on the device without proper permissions.
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< 5.1.47< 5.0.63CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Samsung Pay is installedCheck device applications list for 'Samsung Pay' or 'Samsung Pay Kr' app package (com.samsung.android.spay or com.samsung.android.spay.kr)Affected if Samsung Pay app is present on the device
-
Retrieve Samsung Pay version (Global)Go to Settings > Apps > Samsung Pay > App info, or use ADB command: 'adb shell dumpsys package com.samsung.android.spay | grep versionName'Affected if Version is displayed and is below 5.1.47
-
Retrieve Samsung Pay Kr version (Korea)Go to Settings > Apps > Samsung Pay Kr > App info, or use ADB command: 'adb shell dumpsys package com.samsung.android.spay.kr | grep versionName'Affected if Version is displayed and is below 5.0.63
-
Confirm MTransferNotificationManager is accessibleThis internal component is invoked during MTransfer (money transfer) notification handling; verify by checking if Samsung Pay has been used for money transfer featuresAffected if App version is vulnerable AND money transfer feature has been used, enabling the exposed Pending Intent pathway
User is affected if Samsung Pay (Global version below 5.1.47 or Korea version below 5.0.63) is installed and the money transfer notification feature has been used, allowing malicious apps to hijack the implicit Pending Intent.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.0.635.1.47
Update Samsung Pay to version 5.0.63 (for Korea) or 5.1.47 (for Global) or later, which contains Samsung's fix for this vulnerability.
Samsung Pay 5.1.47 (Global) or Samsung Pay 5.0.63 (Korea)
- Open the Google Play Store or Samsung Galaxy Store on your device
- Search for 'Samsung Pay'
- If an update is available, tap 'Update' to install version 5.1.47 (Global) or 5.0.63 (Korea)
- Alternatively, enable auto-updates for Samsung Pay in your app store settings to receive future security updates
- After updating, verify the version in Samsung Pay > Settings > About Samsung Pay
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-36870 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36870 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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