dbcve.org
SafariWeb browser · Apple

CVE-2018-4113

MEDIUM · 6.5 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 2.20.4 / 4.3 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. tvOS before 11.3 is affected. watchOS before 4.3 is affected. The issue involves a JavaScriptCore function in the "WebKit" component. It allows attackers to trigger an assertion failure by leveraging improper array indexing.

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

This is a vulnerability in WebKit's JavaScriptCore component affecting multiple Apple products (iOS, Safari, iCloud for Windows, iTunes, tvOS, and watchOS). The issue involves improper array indexing that allows remote attackers to trigger an assertion failure, causing a denial-of-service condition via malicious web content.

MitigationApply vendor-supplied updates: upgrade iOS to 11.3+, Safari to 11.1+, iCloud for Windows to 7.4+, iTunes to 12.7.4+, tvOS to 11.3+, and watchOS to 4.3+. This is a network-exploitable issue likely requiring user interaction (visiting malicious website).

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
Iphone OsOperating system
Affected:< 11.3
TvosOperating system
Affected:< 11.3
WatchosOperating system
Affected:< 4.3
IcloudApplication
Affected:< 7.4
ItunesApplication
Affected:< 12.7.4
Webkitgtk\+Web browser
Affected:< 2.20.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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 installed Apple or WebKit product
    Determine which product is installed: Safari, iOS, tvOS, watchOS, iCloud for Windows, iTunes, or WebKitGTK+. Check system settings, About menu, or package manager.
    Affected if Any of these products are installed and the version falls within the affected ranges below.
  2. Check Safari version
    On macOS, open Safari > About Safari. On Windows, open iTunes > Help > About iTunes (Safari included). Compare the displayed version number to 11.1.
    Affected if Safari version is lower than 11.1 (e.g., 11.0.x or earlier).
  3. Check iOS version
    Go to Settings > General > About on iPhone or iPad. Note the Version number (e.g., 11.2.6).
    Affected if iOS version is lower than 11.3 (e.g., 11.2.x or earlier).
  4. Check tvOS or watchOS version
    On Apple TV: go to Settings > General > About > Version. On Apple Watch: open Watch app on iPhone > General > About.
    Affected if tvOS version is lower than 11.3, or watchOS version is lower than 4.3.
  5. Check iTunes or iCloud for Windows version
    Open iTunes > Help > About iTunes. For iCloud Windows, open iCloud control panel or check installed programs list.
    Affected if iTunes version is lower than 12.7.4, or iCloud for Windows version is lower than 7.4.
  6. Check WebKitGTK+ version
    Run `dpkg -l libwebkit2gtk-4.0-37` on Debian/Ubuntu, or check the package version via package manager.
    Affected if WebKitGTK+ version is lower than 2.20.4.

The environment is affected if any of the installed products (Safari, iOS, tvOS, watchOS, iTunes, iCloud for Windows, or WebKitGTK+) have versions below the thresholds listed (11.1 for Safari, 11.3 for iOS/tvOS/watchOS, 12.7.4 for iTunes, 7.4 for iCloud, 2.20.4 for WebKitGTK+).

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 2.20.4 / 4.3 / 7.4 or later
Fixed in 2.20.44.37.4
Interim mitigation

Apply vendor-supplied updates: upgrade iOS to 11.3+, Safari to 11.1+, iCloud for Windows to 7.4+, iTunes to 12.7.4+, tvOS to 11.3+, and watchOS to 4.3+. This is a network-exploitable issue likely requiring user interaction (visiting malicious website).

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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