CVE-2022-36870
First published: Fri Sep 09 2022(Updated: )
Pending 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.
Credit: mobile.security@samsung.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Samsung Pay | <5.1.47 | |
| Samsung Pay | <5.0.63 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2022-36870?
CVE-2022-36870 is classified as a high-severity vulnerability due to its potential to allow unauthorized access to files.
How do I fix CVE-2022-36870?
To fix CVE-2022-36870, update Samsung Pay to version 5.0.63 or later for KR users and version 5.1.47 or later for Global users.
What does CVE-2022-36870 allow attackers to do?
CVE-2022-36870 allows attackers to access files without permission through implicit Intent due to a Pending Intent hijacking vulnerability.
Which versions of Samsung Pay are affected by CVE-2022-36870?
Samsung Pay versions prior to 5.0.63 for KR and earlier than 5.1.47 for Global are affected by CVE-2022-36870.
Is CVE-2022-36870 specific to a certain region?
Yes, CVE-2022-36870 specifically affects Samsung Pay versions for KR and Global regions.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/author
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/samsung
- canonical/samsung pay