dbcve.org
SafariWeb browser · Apple

CVE-2017-2377

HIGH · 7.5 CVSS v3.0 Published 2017-04-02
Fix available
A fix is available. Upgrade to after 10.2.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.3 is affected. Safari before 10.1 is affected. The issue involves the "WebKit Web Inspector" component. It allows attackers to cause a denial of service (memory corruption and application crash) by leveraging a window-close action during a debugger-pause state.

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 the WebKit Web Inspector component allows attackers to cause a denial of service (application crash) by closing a browser window while the debugger is in a paused state. This affects Safari before version 10.1 and iOS devices before version 10.3.

MitigationUpdate Safari to version 10.1 or later, and update iOS devices to version 10.3 or later to receive the patched WebKit component.

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

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari, or run `defaults read /Applications/Safari.app/Contents/Info CFBundleVersion` in Terminal
    Affected if The displayed version is 10.0.3 or earlier (vulnerable range: 10.0.3 and below)
  2. Check iOS version on iPhone or iPad
    Open Settings > General > About, look at the Version field
    Affected if The version shows 10.2.1 or earlier (vulnerable range: 10.2.1 and below)
  3. Verify Web Inspector debugger usage
    Open Safari, enable Develop menu in Preferences > Advanced, then open the Web Inspector (Develop > Show Web Inspector) and pause script execution using a breakpoint, then close the browser window while paused
    Affected if The browser crashes upon closing the window while the debugger is paused at a breakpoint - this confirms the vulnerability is triggerable

A user is affected if they are running Safari 10.0.3 or earlier on macOS, or iOS 10.2.1 or earlier on an iPhone/iPad, AND they use the Web Inspector debugger with breakpoints.

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 a release after 10.2.1
Interim mitigation

Update Safari to version 10.1 or later, and update iOS devices to version 10.3 or later to receive the patched WebKit component.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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