SafariWeb browser · Apple
CVE-2015-1076
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, as used in Apple Safari before 6.2.4, 7.x before 7.1.4, and 8.x before 8.0.4, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site, a different vulnerability than other CVEs listed in APPLE-SA-2015-03-17-1.
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 confidenceMemory corruption vulnerability in WebKit (used by Apple Safari) allows remote code execution or denial of service via maliciously crafted webpages. Affected versions are Safari before 6.2.4, 7.x before 7.1.4, and 8.x before 8.0.4. This is a client-side code execution vulnerability in the browser's rendering engine.
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.3= 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.2<= 12.1<= 7.1CVSS 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, or go to Safari > Settings (or Preferences) > General and look at the version number displayed.Affected if Version is 6.2.3 or lower, or 7.0.x through 7.1.3, or 8.0.3 or lower (versions before 6.2.4, 7.1.4, and 8.0.4 respectively).
-
Check iOS version on iPhone or iPadOpen Settings app > General > About > Version. This displays the iOS version number.Affected if iOS version is 8.2 or lower (iOS 8.2 and earlier). Note: This affects Safari on iOS via the WebKit component.
-
Check iTunes version on Windows or MacOpen iTunes > Help > About iTunes. The version number is displayed in the window that opens.Affected if iTunes version is 12.1 or lower (iTunes 12.1 and earlier). Note: This affects the iTunes Store browsing functionality using WebKit.
-
Check tvOS version on Apple TVGo to Settings > General > About > Version on the Apple TV device.Affected if tvOS version is 7.1 or lower (tvOS 7.1 and earlier). Note: This affects Safari on Apple TV.
A system is affected if Safari (or WebKit-based browsing via iTunes or on iOS/tvOS) is running a version before 6.2.4 (for 6.x), before 7.1.4 (for 7.x), before 8.0.4 (for 8.x), or if iOS is 8.2 or earlier, iTunes is 12.1 or earlier, or tvOS is 7.1 or earlier.
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 Safari to version 6.2.4, 7.1.4, 8.0.4 or later to obtain the patched WebKit component. Organizations should verify all client systems have applied the update.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1076 — 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-1076 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