dbcve.org
SafariWeb browser · Apple

CVE-2017-2354

HIGH · 8.8 CVSS v3.0 Published 2017-02-20
Fix available
A fix is available. Upgrade to 2.16.3 / 6.1.1 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
An issue was discovered in certain Apple products. iOS before 10.2.1 is affected. Safari before 10.0.3 is affected. iCloud before 6.1.1 is affected. iTunes before 12.5.5 is affected. tvOS before 10.1.1 is affected. The issue involves the "WebKit" component. It allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) 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

A memory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause denial of service by tricking users into visiting crafted malicious websites. The vulnerability affects iOS, Safari, iCloud, iTunes, and tvOS via the WebKit rendering component.

MitigationUpdate all affected Apple products to the patched versions: iOS 10.2.1+, Safari 10.0.3+, iCloud 6.1.1+, iTunes 12.5.5+, and tvOS 10.1.1+ or later.

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:< 10.0.3
Iphone OsOperating system
Affected:< 10.2.1
IcloudApplication
Affected:< 6.1.1
ItunesApplication
Affected:< 12.5.5
TvosOperating system
Affected:< 10.1.1
Webkitgtk\+Web browser
Affected:< 2.16.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
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 product using WebKit
    Determine if your system runs Safari, iOS, iCloud, iTunes, tvOS, or an application using WebKitGTK+. For desktop systems, check installed Apple software via the application menu (Safari > About Safari), iTunes (Help > About iTunes), or system package managers. For mobile devices, check Settings > General > About. For Linux systems using WebKit, check the installed webkit2gtk or webkitgtk package version using your package manager (dpkg -l, rpm -qa, or similar).
    Affected if The product is any Apple software listed or WebKitGTK+ below the patched versions.
  2. Check Safari version
    Open Safari and go to Safari > About Safari (on macOS) or open Settings > Safari > About on iOS. Compare the displayed version number to 10.0.3.
    Affected if Safari version is earlier than 10.0.3.
  3. Check iOS version
    On the iOS device, go to Settings > General > About and note the version number. Compare to 10.2.1.
    Affected if iOS version is earlier than 10.2.1.
  4. Check iTunes version
    Open iTunes and go to Help > About iTunes. The version is displayed in the window that opens. Compare to 12.5.5.
    Affected if iTunes version is earlier than 12.5.5.
  5. Check iCloud and tvOS versions
    For iCloud on Windows, open iCloud from the system tray or Start menu and check the version. For tvOS, go to Settings > General > About on the Apple TV device. Compare iCloud to 6.1.1 and tvOS to 10.1.1.
    Affected if iCloud is earlier than 6.1.1 or tvOS is earlier than 10.1.1.
  6. Check WebKitGTK+ version on Linux
    Run the package manager command to query the webkit2gtk or webkitgtk package version. For Debian/Ubuntu: dpkg -l | grep -i webkit. For Red Hat/Fedora: rpm -qa | grep -i webkit. Compare the version number to 2.16.3.
    Affected if WebKitGTK+ version is earlier than 2.16.3.

You are affected if any Apple product using WebKit (Safari, iOS, iTunes, iCloud, tvOS) or WebKitGTK+ on your system is installed at a version lower than the respective patched version listed in the affected 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.16.3 / 6.1.1 / 10.0.3 or later
Fixed in 2.16.36.1.110.0.3
Interim mitigation

Update all affected Apple products to the patched versions: iOS 10.2.1+, Safari 10.0.3+, iCloud 6.1.1+, iTunes 12.5.5+, and tvOS 10.1.1+ or later.

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-2017-2354 — 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-2017-2354 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