{"id":"CVE-2012-3740","url":"https://www.cyber-defence.io/tools/cve/CVE-2012-3740","generatedAt":"2026-10-28T03:22:09.925Z","title":"The Passcode Lock implementation in Apple iOS before 6 does not properly manage the lock state, which allows physically proximate attackers to bypass an intended passcode requirement via unspecified vectors.","description":"The Passcode Lock implementation in Apple iOS before 6 does not properly manage the lock state, which allows physically proximate attackers to bypass an intended passcode requirement via unspecified vectors.","published":"2012-09-20T21:55:04.000Z","lastModified":"2026-06-16T23:43:51.000Z","status":"Modified","sourceIdentifier":"product-security@apple.com","cvss":{"version":"2.0","score":2.1,"severity":"LOW","vector":"AV:L/AC:L/Au:N/C:N/I:P/A:N"},"cwe":["CWE-264"],"affected":["apple/iphone os"],"epss":{"score":0.00316,"percentile":0.24276,"date":"2026-10-26","history":[]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"low","text":"Lower severity and a low EPSS score (0.32%). Track it; it rarely justifies an emergency change on its own."},"changes":[],"references":[{"url":"http://lists.apple.com/archives/security-announce/2012/Sep/msg00003.html","tags":["Vendor Advisory"],"source":"product-security@apple.com"},{"url":"http://support.apple.com/kb/HT5503","tags":["Vendor Advisory"],"source":"product-security@apple.com"},{"url":"http://lists.apple.com/archives/security-announce/2012/Sep/msg00003.html","tags":["Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"},{"url":"http://support.apple.com/kb/HT5503","tags":["Vendor Advisory"],"source":"af854a3a-2127-422b-91ae-364da2661108"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2012-3740","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}