dbcve.org
SafariOperating system · Apple

CVE-2017-2495

MEDIUM · 6.5 CVSS v3.0 Published 2017-05-22
Fix available
A fix is available. Upgrade to after 10.3.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 10.3.2 is affected. Safari before 10.1.1 is affected. The issue involves the "Safari" component. It allows remote attackers to cause a denial of service (application crash) via a crafted web site that improperly interacts with the history menu.

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 client-side denial of service vulnerability in Safari's history menu handling. Attackers can crash the Safari browser by tricking users into visiting a specially crafted website that manipulates the history menu in an unexpected way, causing the application to terminate unexpectedly.

MitigationUpdate Safari to version 10.1.1 or later (and iOS devices to 10.3.2 or later) to patch the vulnerability. Users should avoid visiting untrusted websites until patches are applied.

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
SafariOperating system
Affected:<= 10.1
Iphone OsOperating system
Affected:<= 10.3.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
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. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari. The version number is displayed next to 'Safari'.
    Affected if Version number is 10.1 or earlier
  2. Check iOS version on iPhone or iPad
    Open Settings app > General > About. Look for the 'Version' field which shows iOS version number.
    Affected if Version number is 10.3.1 or earlier (e.g., 10.3, 10.2, 10.1, etc.)
  3. Verify the vulnerability trigger condition
    The flaw is triggered when a user visits a specially crafted website that manipulates Safari's history menu. There is no local configuration to check - the vulnerability exists in the browser code itself.
    Affected if Running affected Safari or iOS version and visiting a malicious website can trigger the crash

You are affected if Safari version is 10.1 or earlier on macOS, or iOS version is 10.3.1 or earlier on iPhone/iPad.

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.3.1
Interim mitigation

Update Safari to version 10.1.1 or later (and iOS devices to 10.3.2 or later) to patch the vulnerability. Users should avoid visiting untrusted websites until patches are applied.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.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-2017-2495 — 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-2495 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