dbcve.org
SafariWeb browser · Apple

CVE-2018-4117

MEDIUM · 6.5 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 4.3 / 11.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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. Safari before 11.1 is affected. iCloud before 7.4 on Windows is affected. iTunes before 12.7.4 on Windows is affected. watchOS before 4.3 is affected. The issue involves the fetch API in the "WebKit" component. It allows remote attackers to bypass the Same Origin Policy and obtain sensitive information via a crafted web site.

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

The WebKit fetch API in certain Apple products contains a Same Origin Policy bypass vulnerability. Attackers can craft a malicious website to make cross-origin fetch() requests and read sensitive responses from other domains, violating the browser security model that normally isolates websites from each other's data.

MitigationApply vendor-supplied patches by updating all affected Apple products (iOS to 11.3+, Safari to 11.1+, iCloud/iTunes to latest, watchOS to 4.3+) to remediate the WebKit 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
SafariWeb browser
Affected:< 11.1
Ubuntu LinuxOperating system
Affected:= 16.04= 17.10
Debian LinuxOperating system
Affected:= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
Iphone OsOperating system
Affected:< 11.3
WatchosOperating system
Affected:< 4.3

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 Safari version on macOS
    Open Safari, click Safari menu > About Safari, or run `defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString` in Terminal
    Affected if Version is lower than 11.1
  2. Check iOS version on iPhone or iPad
    Go to Settings > General > About, or connect device to computer and check in iTunes/Finder
    Affected if Version is lower than 11.3
  3. Check watchOS version on Apple Watch
    Open Watch app on iPhone > My Watch > General > About, or check on Apple Watch in Settings > General > About
    Affected if Version is lower than 4.3
  4. Check for WebKit-based browsers on Ubuntu
    Run `dpkg -l | grep -i webkit` or check installed packages via package manager
    Affected if WebKit browser packages are installed from affected Ubuntu versions (16.04 or 17.10) and remain unpatched
  5. Check for WebKit-based browsers on Debian
    Run `dpkg -l | grep -i webkit` or check installed packages
    Affected if WebKit browser packages are installed on Debian 9.0 and remain unpatched
  6. Check for WebKit on RHEL 6
    Run `rpm -qa | grep -i webkit` to list installed WebKit packages
    Affected if WebKit packages are installed on RHEL 6.0 and remain unpatched

You are affected if you run any Safari version below 11.1, iOS below 11.3, watchOS below 4.3, or unpatched WebKit-based browsers on Ubuntu 16.04/17.10, Debian 9.0, or RHEL 6.0.

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 4.3 / 11.1 / 11.3 or later
Fixed in 4.311.111.3
Interim mitigation

Apply vendor-supplied patches by updating all affected Apple products (iOS to 11.3+, Safari to 11.1+, iCloud/iTunes to latest, watchOS to 4.3+) to remediate the WebKit vulnerability.

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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