dbcve.org
SafariWeb browser · Apple

CVE-2016-4758

MEDIUM · 6.5 CVSS v3.0 Published 2016-09-25
Fix available
A fix is available. Upgrade to after 12.4.3 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
WebKit in Apple iOS before 10, iTunes before 12.5.1 on Windows, and Safari before 10 does not properly restrict access to the location variable, which allows remote attackers to obtain sensitive information 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

WebKit fails to properly restrict access to the location variable, allowing malicious websites to obtain sensitive location information without proper user consent or restrictions.

MitigationUpdate affected Apple products (iOS to version 10+, iTunes to 12.5.1+, Safari to version 10+) to obtain the patched WebKit component. Avoid untrusted websites as a interim measure.

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:<= 9.1.3
Iphone OsOperating system
Affected:<= 9.3.5
ItunesApplication
Affected:<= 12.4.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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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. Check Safari version
    Open Safari on macOS and click Safari in the menu bar, then select About Safari. The version number appears in the window that opens.
    Affected if The version displayed is 9.1.3 or lower (for example, 9.1.2, 9.1.1, 9.0.x)
  2. Check iOS version
    On iPhone or iPad, open the Settings app, tap General, then tap About. The Version field shows the installed iOS version.
    Affected if The version displayed is 9.3.5 or lower (for example, 9.3.4, 9.3.3, 9.2.x, 9.1.x, 9.0.x)
  3. Check iTunes version
    Open iTunes on Windows or macOS, then go to Help in the menu bar and select About iTunes. The version number appears in the dialog box.
    Affected if The version displayed is 12.4.3 or lower (for example, 12.4.2, 12.4.1, 12.4.0)

You are affected if any Apple product (Safari, iOS, or iTunes) installed on your device matches or is below the specified vulnerable versions, since the unpatched WebKit component allows unauthorized website access to geolocation data.

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 12.4.3
Interim mitigation

Update affected Apple products (iOS to version 10+, iTunes to 12.5.1+, Safari to version 10+) to obtain the patched WebKit component. Avoid untrusted websites as a interim measure.

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-2016-4758 — 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-2016-4758 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