What is the severity of CVE-2022-36872?

CVE-2022-36872 is classified as a high severity vulnerability due to its potential for unauthorized file access.

How can I fix CVE-2022-36872?

To fix CVE-2022-36872, update Samsung Pay to version 5.0.63 for KR or 5.1.47 for Global.

What type of vulnerability is CVE-2022-36872?

CVE-2022-36872 is a Pending Intent hijacking vulnerability that affects Samsung Pay.

Which versions of Samsung Pay are affected by CVE-2022-36872?

CVE-2022-36872 affects versions of Samsung Pay prior to 5.0.63 for KR and 5.1.47 for Global.

What can attackers achieve with CVE-2022-36872?

Attackers exploiting CVE-2022-36872 can access files without permission via implicit Intent.

Vulnerability/
CVE-2022-36872

medium

6.5

CWE

285

9/9/2022

3/8/2024

CVE-2022-36872

First published: Fri Sep 09 2022(Updated: )

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.

Credit: mobile.security@samsung.com

Affected Software	Affected Version	How to fix
Samsung Samsung Pay	<5.1.47
Samsung Samsung Pay Kr	<5.0.63

Never miss a vulnerability like this again

Reference Links

https://security.samsungmobile.com/serviceWeb.smsb?year=2022&month=09

Frequently Asked Questions

What is the severity of CVE-2022-36872?
CVE-2022-36872 is classified as a high severity vulnerability due to its potential for unauthorized file access.
How can I fix CVE-2022-36872?
To fix CVE-2022-36872, update Samsung Pay to version 5.0.63 for KR or 5.1.47 for Global.
What type of vulnerability is CVE-2022-36872?
CVE-2022-36872 is a Pending Intent hijacking vulnerability that affects Samsung Pay.
Which versions of Samsung Pay are affected by CVE-2022-36872?
CVE-2022-36872 affects versions of Samsung Pay prior to 5.0.63 for KR and 5.1.47 for Global.
What can attackers achieve with CVE-2022-36872?
Attackers exploiting CVE-2022-36872 can access files without permission via implicit Intent.

collector/nvd-index
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/references
agent/last-modified-date
agent/severity
agent/weakness
agent/author
agent/description
agent/tags
agent/first-publish-date
agent/event
agent/source
vendor/samsung
canonical/samsung samsung pay
canonical/samsung samsung pay kr

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-36872?
CVE-2022-36872 is classified as a high severity vulnerability due to its potential for unauthorized file access.
How can I fix CVE-2022-36872?
To fix CVE-2022-36872, update Samsung Pay to version 5.0.63 for KR or 5.1.47 for Global.
What type of vulnerability is CVE-2022-36872?
CVE-2022-36872 is a Pending Intent hijacking vulnerability that affects Samsung Pay.
Which versions of Samsung Pay are affected by CVE-2022-36872?
CVE-2022-36872 affects versions of Samsung Pay prior to 5.0.63 for KR and 5.1.47 for Global.
What can attackers achieve with CVE-2022-36872?
Attackers exploiting CVE-2022-36872 can access files without permission via implicit Intent.