dbcve.org
Iphone OsOperating system · Apple

CVE-2018-4380

MEDIUM · 5.5 CVSS v3.0 Published 2019-04-03
Fix available
A fix is available. Upgrade to 12.1 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A lock screen issue allowed access to photos and contacts on a locked device. This issue was addressed by restricting options offered on a locked device. This issue affected versions prior to iOS 12.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

iOS lock screen bypass vulnerability in versions prior to 12.0.1 that allowed unauthorized access to photos and contacts through insufficiently restricted lock screen options. The flaw permitted interaction with sensitive data without device authentication.

MitigationUpdate affected iOS devices to version 12.0.1 or later to enforce proper lock screen restrictions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Iphone OsOperating system
Affected:< 12.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check iOS version
    Go to Settings > General > About and look at the 'Version' field. Compare this number to 12.1.
    Affected if The iOS version is less than 12.1
  2. Identify lock screen widget configuration
    From the lock screen, swipe left to view widgets or check Settings > Face ID & Passcode (or Touch ID & Passcode) > Lock Screen to see which apps and features are accessible when the device is locked.
    Affected if Apps or widgets that can access photos or contacts are enabled on the lock screen (such as Siri, Camera, or third-party widgets with sensitive data access)
  3. Test lock screen data exposure
    From a locked state, attempt to use any exposed shortcuts or widgets to access photos or contacts without authenticating (entering passcode or using biometrics).
    Affected if Photos or contacts can be viewed or interacted with without first unlocking the device with authentication

A device is affected if it runs iOS version 12.0 or earlier AND has lock screen widgets or shortcuts enabled that expose photos or contacts without requiring device authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 12.1 or later
Fixed in 12.1
Interim mitigation

Update affected iOS devices to version 12.0.1 or later to enforce proper lock screen restrictions.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,032.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-4380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-4380 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data