SafariWeb browser · Apple
CVE-2015-1128
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 · uneditedThe private-browsing implementation in Apple Safari before 6.2.5, 7.x before 7.1.5, and 8.x before 8.0.5 allows attackers to obtain sensitive browsing-history information via vectors involving push-notification requests.
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 confidenceIn Safari versions prior to 6.2.5, 7.1.5, and 8.0.5, the private-browsing mode failed to properly isolate browsing history from push-notification requests. Attackers could craft malicious push notifications that could leak sensitive browsing-history information from private sessions.
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.4= 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.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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Safari versionOpen Safari and select Safari > About Safari (on macOS). Record the version number shown (e.g., 7.1.4 or 8.0.4).Affected if The version is 6.2.4 or lower, or exactly 7.0.x through 7.1.3, or 8.0.4 or lower.
-
Verify private browsing mode is in useLook for the private-browsing indicator in Safari: the address bar should show 'Private' or the menu bar should show a dimmed private-browsing icon.Affected if Private browsing mode is currently active while using a vulnerable Safari version.
-
Confirm push notifications are enabledGo to Safari > Settings > Notifications (or Preferences > Notifications) and check whether 'Allow websites to ask for permission to send push notifications' is enabled.Affected if Push notifications are permitted in the browser settings on a vulnerable version.
-
Determine OS X version for contextClick the Apple menu > About This Mac to see the macOS version (e.g., 10.9 Mavericks, 10.10 Yosemite).Affected if The OS X version combined with Safari version falls outside the patched ranges (6.2.5 for OS X 10.8, 7.1.5 for OS X 10.9, 8.0.5 for OS X 10.10).
You are affected if your Safari version matches any of the listed vulnerable versions (6.2.4 or below, or 7.0 through 7.1.3) AND you use private browsing with push notifications enabled.
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.5 or later for OS X 10.8, 7.1.5 or later for OS X 10.9, or 8.0.5 or later for OS X 10.10 to remediate this vulnerability.
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-1128 — 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-1128 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