dbcve.org
SafariWeb browser · Apple

CVE-2017-7071

HIGH · 8.8 CVSS v3.0 Published 2018-04-03
Fix available
A fix is available. Upgrade to 10.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. Safari before 10.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

Memory corruption vulnerability in WebKit allowing remote arbitrary code execution or denial of service via crafted malicious web pages in Safari before version 10.1.

MitigationUpgrade Safari to version 10.1 or later to patch the vulnerability. As a temporary workaround, disable JavaScript or avoid visiting untrusted websites.

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.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
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. Check if Safari is installed
    On macOS, open Finder > Applications folder and look for Safari.app, or run 'ls /Applications | grep -i safari' in Terminal
    Affected if Safari.app exists on the system
  2. Determine installed Safari version
    Open Safari > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal
    Affected if Version string is retrieved showing a number less than 10.1
  3. Compare version against affected range
    Compare the obtained version number to 10.1 - versions like 10.0.x or earlier are in the affected range
    Affected if Installed version is 10.0.x or earlier (any version < 10.1)
  4. Verify JavaScript is enabled (required for exploit delivery)
    Open Safari > Preferences > Security > Check 'Enable JavaScript' checkbox, or check WebKit preferences
    Affected if JavaScript is enabled and user may visit untrusted websites

User is affected if Safari version is below 10.1 and JavaScript is enabled, allowing malicious web pages to trigger the WebKit memory corruption.

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 10.1 or later
Fixed in 10.1
Interim mitigation

Upgrade Safari to version 10.1 or later to patch the vulnerability. As a temporary workaround, disable JavaScript or avoid visiting untrusted websites.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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