CVE-2015-1065
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 · uneditedMultiple buffer overflows in iCloud Keychain in Apple iOS before 8.2 and Apple OS X through 10.10.2 allow man-in-the-middle attackers to execute arbitrary code by modifying the client-server data stream during keychain recovery.
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 confidenceMultiple buffer overflow vulnerabilities exist in iCloud Keychain sync (keychain recovery) in Apple iOS before 8.2 and OS X through 10.10.2. A man-in-the-middle attacker who can intercept and modify the client-server communication stream during keychain recovery can trigger these overflows and achieve arbitrary code execution.
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.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
- Adjacent
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:A/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 the installed iOS versionOn the iOS device, go to Settings > General > About and note the version number. Compare it to the affected range: iOS <= 8.1.3 is vulnerable; iOS 8.2 and later are patched.Affected if The device runs iOS 8.1.3 or earlier
-
Check the installed macOS versionOn Mac, click the Apple menu > About This Mac and note the OS X version number. Compare it to the affected range: OS X 10.10.2 or earlier is vulnerable; 10.10.3 and later are patched.Affected if The Mac runs OS X 10.10.2 or earlier
-
Verify if iCloud Keychain sync is enabledOn iOS: go to Settings > iCloud > Keychain and check if iCloud Keychain is turned on. On Mac: go to System Preferences > iCloud > Keychain and check if the service is enabled.Affected if iCloud Keychain sync is enabled on a vulnerable OS version
-
Check if keychain recovery is configuredOn iOS: Settings > iCloud > Keychain > iCloud Keychain Recovery. On Mac: System Preferences > iCloud > Keychain > Options, look for keychain recovery settings. Check if a recovery method is configured or has been used.Affected if Keychain recovery is configured or has been initiated on a vulnerable OS version
A user is affected if their device runs a vulnerable OS version (iOS 8.1.3 or earlier, or OS X 10.10.2 or earlier) AND they have iCloud Keychain sync enabled, particularly if keychain recovery has been configured or used.
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 iOS devices to version 8.2 or later and OS X systems to version 10.10.2 or later to obtain Apple's patched version of the iCloud Keychain component.
- Consultation2.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1065 — 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-1065 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