SafariWeb browser · Apple
CVE-2015-3658
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 Page Loading functionality in WebKit 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 consider redirects during decisions about sending an Origin header, which makes it easier for remote attackers to bypass CSRF protection mechanisms 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 · moderate confidenceWebKit's Page Loading functionality in Safari and iOS does not properly handle the Origin header during redirect scenarios. When a request is redirected, the Origin header may not be sent, which breaks CSRF protection mechanisms that rely on the Origin header for cross-origin request validation.
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.
-
Identify browser in useCheck which web browser is configured as the default or currently in use. This vulnerability only affects Safari and WebKit-based browsers on Apple platforms.Affected if The browser is not Safari or is a non-Apple platform browser (the vulnerability is specific to Apple Safari and iOS WebKit)
-
Check Safari version on macOSOpen Safari, then go to Safari > About Safari to display the version number. Note the full version (e.g., 7.0.6, 7.1.2)Affected if The Safari version is 6.2.6 or lower; OR is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, or 7.0.6; OR is 7.1.0, 7.1.1, 7.1.2, or 7.1.3
-
Check iOS version on iPhone or iPadOn the device, go to Settings > General > About and note the iOS version number.Affected if The iOS version is 8.3 or lower
-
Check macOS versionClick the Apple menu > About This Mac to display the macOS version. This helps determine the bundled Safari version.Affected if The macOS version is 10.10.3 or lower (which ships with an affected Safari version)
You are affected if you use Safari on macOS versions 10.10.3 or earlier, or use Safari versions 7.1.3 or earlier on newer macOS, or use iOS 8.3 or earlier on iPhone or iPad.
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.7+, 7.1.7+, or 8.0.7+ and iOS to 8.4+. Alternatively, implement supplemental CSRF protections such as double-submit cookies or custom header requirements that are not vulnerable to redirect-based bypasses.
Fix this in Safari
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3658 — 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-3658 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