dbcve.org
SafariWeb browser · Apple

CVE-2018-4210

HIGH · 8.8 CVSS v3.0 Published 2019-01-11
Fix available
A fix is available. Upgrade to 2.22.0 / 4.3 or later.
See remediation →
95/100
Remediation priority · Urgent
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
In iOS before 11.3, Safari before 11.1, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windows, an array indexing issue existed in the handling of a function in javascript core. This issue was addressed with improved checks.

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 · moderate confidence

An array indexing vulnerability in JavaScriptCore allows an attacker to potentially access or manipulate memory outside the bounds of an array through specially crafted JavaScript code. The vulnerability stems from insufficient bounds checking when handling a specific function, which could lead to heap corruption, information disclosure, or arbitrary code execution.

MitigationApply the vendor-supplied updates: iOS 11.3+, Safari 11.1+, tvOS 11.3+, watchOS 4.3+, or iTunes 12.7.4+ for Windows. For internal applications, audit any JavaScript execution contexts that process untrusted input.

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:= 18.04
Iphone OsOperating system
Affected:< 11.3
TvosOperating system
Affected:< 11.3
WatchosOperating system
Affected:< 4.3
ItunesApplication
Affected:< 12.7.4
Webkitgtk\+Web browser
Affected:< 2.22.0

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
High
Availability
High

CVSS:3.0/AV:N/AC:L/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 the WebKit-based application or component in use
    Determine which application uses JavaScriptCore/WebKit on the system. This could be Safari (macOS/iOS), WebKitGTK-based browsers on Ubuntu, or applications that bundle WebKit.
    Affected if The system runs any WebKit-based browser or application on Ubuntu 18.04, iOS, tvOS, watchOS, or iTunes for Windows.
  2. Check the installed version of Safari
    On macOS, open Safari and go to Safari > About Safari. The version number will be displayed. Compare it to the affected range: versions prior to 11.1 are affected.
    Affected if Safari version is less than 11.1.
  3. Check the installed version of WebKitGTK on Ubuntu
    On Ubuntu 18.04, run 'dpkg -l libwebkit2gtk-4.0-37' or 'dpkg -l webkit2gtk-4.0' to view the installed package version. Alternatively, check the webkit2gtk version via your package manager.
    Affected if WebKitGTK version is less than 2.22.0 on Ubuntu 18.04.
  4. Check iOS, tvOS, or watchOS version on Apple devices
    On the device, go to Settings > General > About to view the iOS/tvOS/watchOS version. Compare against the affected ranges: iOS < 11.3, tvOS < 11.3, watchOS < 4.3.
    Affected if iOS version is less than 11.3, tvOS is less than 11.3, or watchOS is less than 4.3.
  5. Check iTunes version on Windows
    Open iTunes and go to Help > About iTunes. The version will be displayed. Affected versions are prior to 12.7.4.
    Affected if iTunes version is less than 12.7.4 on Windows.

The environment is affected if any WebKit-based application (Safari, WebKitGTK browsers on Ubuntu 18.04, iOS, tvOS, watchOS, or iTunes for Windows) is running a version below the fixed releases specified in the affected version ranges.

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.22.0 / 4.3 / 11.1 or later
Fixed in 2.22.04.311.1
Interim mitigation

Apply the vendor-supplied updates: iOS 11.3+, Safari 11.1+, tvOS 11.3+, watchOS 4.3+, or iTunes 12.7.4+ for Windows. For internal applications, audit any JavaScript execution contexts that process untrusted input.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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