SafariWeb browser · Apple
CVE-2015-3752
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 Content Security Policy implementation in WebKit in Apple Safari before 6.2.8, 7.x before 7.1.8, and 8.x before 8.0.8, as used in iOS before 8.4.1 and other products, does not properly restrict cookie transmission for report requests, which allows remote attackers to obtain sensitive information via vectors involving (1) a cross-origin request or (2) a private-browsing request.
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 Content Security Policy implementation incorrectly transmits cookies with CSP report requests, allowing sensitive information such as session cookies to potentially leak via cross-origin requests or during private-browsing 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.0, < 6.2.8>= 7.0, < 7.1.8>= 8.0, < 8.0.8
Ubuntu LinuxOperating system
= 14.04= 15.10< 8.4.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
- 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.
-
Check Safari version on macOSOpen Safari, go to Safari menu > About Safari to view the version number (e.g., 8.0.7, 7.1.6, 6.2.5)Affected if Version is 6.0 to 6.2.7, 7.0 to 7.1.7, or 8.0 to 8.0.7 (the version displayed is less than 6.2.8, 7.1.8, or 8.0.8 respectively)
-
Check iOS version on iPhone/iPadGo to Settings > General > About on the iOS device and note the version number (e.g., 8.4, 8.3)Affected if Version is earlier than 8.4.1 (the version shown is less than 8.4.1)
-
Check WebKit version on Ubuntu LinuxFor systems with WebKit-based browsers (such as older Ubuntu packages), check the installed webkit version using: dpkg -l | grep -i webkit or rpm -qa | grep -i webkitAffected if Running Ubuntu 14.04 or 15.10 with WebKit packages that have not been patched for this CVE
-
Verify if Content Security Policy is in useInspect web application headers or browser configuration: look for 'Content-Security-Policy' HTTP response header in browser developer tools (Network tab), or check if browsing to sites that set CSP policiesAffected if CSP is actively configured and the browser would send violation reports (the vulnerability only affects environments where CSP report-uri is used)
You are affected if you are running Safari versions 6.0-6.2.7, 7.0-7.1.7, or 8.0-8.0.7; iOS versions before 8.4.1; or Ubuntu 14.04/15.10 with unpatched WebKit, AND you use Content Security Policy with report-uri enabled where cookies could leak in CSP violation reports.
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 data6.2.87.1.88.0.8
Apply Apple's security updates for Safari (6.2.8, 7.1.8, or 8.0.8 and later) and iOS (8.4.1 and later) to patch the CSP bypass in WebKit.
Fix this in Safari
Scoped from the published advisory
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3752 — 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-3752 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