Security readout for executives and security teams
This is an old iPhone lock-screen issue. On iOS versions before 7.0.3, someone physically near the device could bypass the intended passcode requirement in a specific lock-screen state and dial arbitrary phone numbers. Exposure is most likely limited to legacy iPhone devices still running iOS before 7.0.3. The described attack requires physical proximity, not remote network access. Treat this as a legacy-device hygiene issue. Business urgency is low unless the organization still operates affected iPhones or has unmanaged devices with sensitive access. Mitigation focus: Confirm fleet iPhones are updated to iOS 7.0.3 or later.; Retire or isolate devices that cannot be updated.; Check Apple advisory APPLE-SA-2013-10-22-1 for vendor guidance..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2013-5144 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.