dbcve.org
Iphone OsOperating system · Apple

CVE-2018-4151

HIGH · 7.0 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 10.13.4 / 11.3 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges

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
An issue was discovered in certain Apple products. iOS before 11.3 is affected. macOS before 10.13.4 is affected. The issue involves the "iCloud Drive" component. A race condition allows attackers to execute arbitrary code in a privileged context via a crafted app.

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

A race condition vulnerability in the iCloud Drive component on iOS before 11.3 and macOS before 10.13.4 allows a crafted application to achieve arbitrary code execution in a privileged context, representing a local privilege escalation.

MitigationUpdate affected devices to iOS 11.3 or later and macOS 10.13.4 or later to remediate the vulnerability.

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:< 11.3
Mac Os XOperating system
Affected:< 10.13.4

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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify your device OS type
    Determine whether the device runs iOS (iPhone/iPad) or macOS. This CVE affects only these two Apple operating systems.
    Affected if Device runs neither iOS nor macOS (not applicable)
  2. Check iOS version on iPhone or iPad
    Open Settings > General > About on the iOS device. Locate the 'Version' field which displays the installed iOS version number.
    Affected if iOS version is lower than 11.3 (for example, 11.2.6 or earlier)
  3. Check macOS version on Mac computer
    Click the Apple menu > About This Mac. The macOS version number is displayed in the Overview tab (for example, 10.13.3).
    Affected if macOS version is lower than 10.13.4 (for example, 10.13.3 or earlier)
  4. Confirm iCloud Drive is in use
    On iOS, go to Settings > iCloud > iCloud Drive to verify the feature is enabled. On macOS, go to System Preferences > iCloud and ensure iCloud Drive is checked. The vulnerability requires iCloud Drive to be accessible.
    Affected if iCloud Drive is enabled and the OS version is below the fixed releases

Device is affected if it runs iOS below 11.3 or macOS below 10.13.4 AND has iCloud Drive enabled, allowing a local attacker to exploit the race condition for privilege escalation.

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 10.13.4 / 11.3 or later
Fixed in 10.13.411.3
Interim mitigation

Update affected devices to iOS 11.3 or later and macOS 10.13.4 or later to remediate the vulnerability.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-4151 — 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-4151 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