CVE-2015-1089
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 · uneditedCFNetwork in Apple iOS before 8.3 and Apple OS X before 10.10.3 does not properly handle cookies during processing of redirects in HTTP responses, which allows remote attackers to bypass the Same Origin Policy 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 confidenceCFNetwork in Apple iOS before 8.3 and OS X before 10.10.3 improperly handles cookies during HTTP redirect processing, allowing attackers to bypass the Same Origin Policy and potentially access cookies from other origins via a crafted website.
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<= 10.10.2<= 8.2CVSS 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 the installed OS X versionRun 'sw_vers' in Terminal or click Apple menu > About This Mac to view the exact OS version numberAffected if The version is 10.10.2 or lower (vulnerable). Versions 10.10.3 and above are patched.
-
Check the installed iOS versionOn iOS device, go to Settings > General > About > Version to view the iOS versionAffected if The version is 8.2 or lower (vulnerable). Versions 8.3 and above are patched.
-
Identify CFNetwork usage in custom applicationsSearch application binaries or source code for references to CFNetwork framework imports (e.g., '#import <CFNetwork/CFNetwork.h>' in Objective-C, or linkage to CFNetwork library)Affected if The application links against CFNetwork and processes HTTP cookies during redirects, making it affected by the vulnerable code path.
-
Inspect system proxy or network interception configurationCheck System Preferences > Network > Advanced > Proxies on OS X, or Settings > Wi-Fi > Info > HTTP Proxy on iOS for any manually configured proxy settings that handle redirectsAffected if A custom proxy or network tool that relies on CFNetwork cookie handling is in use, potentially exposing cookie data during redirect scenarios.
A user is affected if they are running OS X 10.10.2 or earlier, or iOS 8.2 or earlier, and their applications or browsers process HTTP cookies through redirects using the CFNetwork framework.
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 devices to iOS 8.3+ or OS X 10.10.3+ to patch CFNetwork. For applications using CFNetwork directly, ensure proper cookie validation after redirects.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1089 — 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-1089 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