Iphone OsOperating system · Apple

CVE-2015-3776

HIGH · 9.3 CVSS v2.0 Published 2015-08-16
Fix available
A fix is available. Upgrade to after 10.10.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
IOKit in Apple iOS before 8.4.1 and OS X before 10.10.5 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption and application crash) via a malformed plist.

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 confidence

IOKit's plist parsing functionality contains a memory corruption vulnerability when handling malformed property list files. Successful exploitation allows an attacker to execute arbitrary code in a privileged context (kernel/root) or cause a denial of service via application crash.

MitigationApply Apple's security updates: upgrade iOS to version 8.4.1 or later, and upgrade OS X to version 10.10.5 or later.

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
Iphone OsOperating system
Affected:<= 8.4
Mac Os XOperating system
Affected:<= 10.10.4

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your operating system
    Determine whether the system is running Apple iOS or macOS. On iOS, check Settings > General > About. On macOS, click the Apple menu and select About This Mac.
    Affected if System is Apple iPhone OS or Apple Mac OS X
  2. Check iOS version
    On iOS device, go to Settings > General > About and note the Version number (e.g., 8.4).
    Affected if iOS version is 8.4 or earlier
  3. Check macOS version
    On Mac, click Apple menu > About This Mac and note the version number (e.g., 10.10.4).
    Affected if macOS version is 10.10.4 or earlier (e.g., 10.10.0 through 10.10.4)
  4. Verify IOKit framework presence
    IOKit is a core framework present by default in iOS and macOS. On macOS, you can run 'ls /System/Library/Frameworks/IOKit.framework' in Terminal to confirm it exists.
    Affected if IOKit framework is present (which is true for all standard iOS/macOS installations)
  5. Confirm plist processing vectors
    IOKit's plist parsing is invoked when applications or system services load property list files. There is no user-configurable toggle; this is core system functionality. The vulnerability is present in the IOKit version bundled with the affected OS versions above.
    Affected if Running any iOS version <= 8.4 or macOS version <= 10.10.4 with standard IOKit plist parsing in use

You are affected if the system runs iOS 8.4 or earlier, or macOS 10.10.4 or earlier, as these versions contain the vulnerable IOKit plist parsing code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 10.10.4
Interim mitigation

Apply Apple's security updates: upgrade iOS to version 8.4.1 or later, and upgrade OS X to version 10.10.5 or later.

Recommended fix High confidence

iOS 8.4.1+ and OS X 10.10.5+

  1. For iOS devices: Go to Settings > General > Software Update and install iOS 8.4.1 or later
  2. For Mac OS X computers: Go to Apple Menu > Software Update and install OS X 10.10.5 or later
  3. Alternatively, download iOS 8.4.1 from Apple's official iOS restore page and Mac OS X 10.10.5 from the Mac App Store
  4. After updating, verify the version in Settings > General > About (iOS) or Apple Menu > About This Mac (OS X)
Caveat Ensure backup of important data before upgrading; some legacy applications may not be compatible with updated OS versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-3776 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-3776 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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