Security readout for executives and security teams
Plain-English summary
CVE-2018-4379 is an Apple iOS lock screen flaw where a locked device could still expose the share function. The available sources say Apple fixed it in iOS 12.0.1 by restricting options shown while locked. Business risk is mainly privacy and data exposure on outdated devices, not confirmed remote compromise.
Executive priority
Treat this as a legacy mobile privacy exposure. It should not outrank actively exploited vulnerabilities, but any remaining pre-12.0.1 iOS devices should be updated or removed from sensitive use.
Technical view
The issue affects iOS versions before 12.0.1. Apple describes it as a lock screen issue allowing access to the share function on a locked device. No CVSS, CWE, detailed attack prerequisites, or affected device model list is provided in the source bundle.
Likely exposure
Exposure is limited to devices running iOS versions prior to 12.0.1. Current managed fleets should be exposed only if legacy, unmanaged, or unsupported iOS devices remain in use.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. The described context is a locked iOS device; sources do not document remote exploitation, exploit maturity, or weaponized public details.
Researcher notes
Public details are sparse. The available record identifies the vulnerable behavior and fixed version, but not CVSS, CWE, exact UI path, affected hardware models, or exploit reliability. Avoid assumptions beyond Apple’s lock-screen share-function description.
Mitigation direction
- Update affected iOS devices to iOS 12.0.1 or later.
- Identify and retire devices that cannot reach a fixed iOS version.
- Prioritize devices used for sensitive communications or regulated data.
- If upgrade is blocked, check Apple guidance before relying on compensating controls.
Validation and detection
- Inventory all iOS devices and record installed versions.
- Flag any device running iOS earlier than 12.0.1.
- Confirm endpoint management reports successful update compliance.
- Review exceptions for unsupported or unmanaged legacy devices.
Public sources used
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-2018-4379 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
- https://support.apple.com/kb/HT209162CVE reference · x_refsource_MISC
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.