dbcve.org
SafariWeb browser · Apple

CVE-2017-2376

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 "Safari" component. It allows remote attackers to spoof the address bar by leveraging text input during the loading of a page.

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 an address bar spoofing vulnerability in Safari where remote attackers can manipulate the displayed URL in the address bar during page loading through text input, potentially tricking users into believing they're on a different website than they actually are.

MitigationUpgrade to iOS 10.3 or later, or Safari 10.1 or later, to resolve the address bar spoofing vulnerability.

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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 Apple product in use
    Determine whether the environment uses Safari web browser (on macOS) or iOS (on iPhone/iPad)
    Affected if The device runs Safari or iOS and is within the affected product line
  2. Check Safari version on macOS
    Open Safari, click Safari menu, select About Safari, and note the version number displayed (e.g., 10.0.3)
    Affected if The displayed version is 10.0.3 or lower
  3. Check iOS version on iPhone or iPad
    Open Settings app, tap General, tap About, and note the Version field (e.g., 10.2.1)
    Affected if The displayed version is 10.2.1 or lower
  4. Compare against affected ranges
    Match your identified version to the affected version ranges: Safari <= 10.0.3 or iPhone OS (iOS) <= 10.2.1
    Affected if Your installed version falls within or below these thresholds

You are affected if Safari is version 10.0.3 or lower, or if iOS is version 10.2.1 or lower, since the address bar spoofing vulnerability exists in those versions.

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

Upgrade to iOS 10.3 or later, or Safari 10.1 or later, to resolve the address bar spoofing vulnerability.

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-2376 — 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-2376 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