# CVE-2011-3440: Security feature bypass in n/a

> Physically proximate attackers can bypass the iOS Passcode Lock by opening the Smart Cover during power-off confirmation, accessing device data.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Nov 2011
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4wgp-qw6c-r96h

## What is CVE-2011-3440?

CVE-2011-3440 is a low-severity vulnerability in Apple Iphone Os, published on 11 Nov 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Passcode Lock feature in Apple iOS before 5.0.1 on the iPad 2 does not properly implement the locked state, which allows physically proximate attackers to access data by opening a Smart Cover during power-off confirmation.

Weakness: CWE-264

## Which versions are affected by CVE-2011-3440?

It affects 2 products.


Products: Apple Ipad2, Apple Iphone Os.

## How do I fix CVE-2011-3440?

No fix has been published for CVE-2011-3440 yet. Limit exposure of the affected software until one is available.

## Is CVE-2011-3440 being exploited?

There is no known exploitation of CVE-2011-3440 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3440 and fix it if it is affected.

What it is: CVE-2011-3440 is a low-severity vulnerability in Apple Iphone Os, published on 11 Nov 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-3440 in the wild and no public exploit code.

Affected product: Apple Iphone Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-3440/ (Markdown: https://insights.sbomify.com/CVE-2011-3440/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-3440
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-3440
- OSV: https://osv.dev/vulnerability/CVE-2011-3440

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-3440/
Summaries are generated and may contain mistakes; the official description above is the record.