SafariWeb browser · Apple
CVE-2015-3727
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 · uneditedWebKit in Apple Safari before 6.2.7, 7.x before 7.1.7, and 8.x before 8.0.7, as used in Apple iOS before 8.4 and other products, does not properly restrict rename operations on WebSQL tables, which allows remote attackers to access an arbitrary web site's database 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 confidenceWebKit's WebSQL implementation failed to properly restrict rename operations on database tables, allowing a malicious origin to rename tables in another origin's database and thereby gain unauthorized access to cross-origin WebSQL data.
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
<= 6.2.6= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.1.0= 7.1.1= 7.1.2= 7.1.3<= 8.3<= 10.10.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari version on macOSOpen Safari, click Safari menu > About Safari. Note the version number shown (e.g., 7.1.2).Affected if Version is 6.2.6 or lower, or any of 7.0.x, 7.0.1.x, 7.0.2.x, 7.0.3.x, 7.0.4.x, 7.0.5.x, 7.0.6.x, or 7.1.0 through 7.1.3.
-
Check iOS version on iPhone/iPadOpen Settings > General > About. Note the Version number (e.g., 8.3).Affected if Version is 8.3 or lower.
-
Check Mac OS X versionClick Apple menu > About This Mac. Note the OS version (e.g., 10.10.3).Affected if OS version is 10.10.3 or lower.
-
Verify WebSQL usage contextThis vulnerability affects WebSQL databases in Safari. WebSQL is a deprecated feature. Check if any web applications in your environment use WebSQL by inspecting browser storage or application code for window.openDatabase calls.Affected if WebSQL is actively used and the Safari/iOS/macOS version falls within the affected ranges above.
You are affected if Safari is version 6.2.6 or below, 7.0.x through 7.1.3, iOS is 8.3 or below, or Mac OS X is 10.10.3 or below, and WebSQL databases are in use.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate affected Apple products (Safari to 6.2.7+, 7.1.7+, or 8.0.7+; iOS to 8.4+) to obtain the patched WebKit version that properly enforces origin-based restrictions on WebSQL table operations.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2015-3727 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-3727 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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