VYPR
Unrated severityNVD Advisory· Published Aug 16, 2015· Updated May 6, 2026

CVE-2015-3776

CVE-2015-3776

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A malformed plist causes memory corruption in Apple's IOKit, allowing arbitrary code execution in kernel context on iOS before 8.4.1 and OS X before 10.10.5.

Vulnerability

A vulnerability exists in Apple's IOKit framework on iOS before 8.4.1 and OS X before 10.10.5. The issue is triggered when IOKit processes a malformed plist (property list), leading to memory corruption. No special configuration is required; the vulnerable code path is present in the default IOKit driver handling for both iOS and OS X [1][2].

Exploitation

An attacker can trigger the vulnerability by delivering a crafted plist to the target system. On iOS, this could be done through a malicious application or via a web page that passes the plist to IOKit through a system service. On OS X, a local attacker or a remote attacker who convinces the user to open a specially crafted file could exploit this. No authentication is required if the attack vector is a crafted file or network request that reaches IOKit. The sequence involves the attacker providing a malformed plist that is parsed by IOKit, causing a memory corruption [1][2].

Impact

Successful exploitation allows an attacker to execute arbitrary code in a privileged kernel context, gaining full control over the device. Alternatively, the attacker could cause a denial of service by triggering a system crash. The impact includes complete compromise of confidentiality, integrity, and availability at the kernel level [1][2].

Mitigation

Apple addressed the vulnerability in iOS 8.4.1, released on August 13, 2015, and in OS X Yosemite v10.10.5 and Security Update 2015-006, released on the same date. Users should update to these versions or later. No workarounds are documented; the only mitigation is installing the software updates [1][2].

AI Insight generated on May 23, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

4

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

6

News mentions

0

No linked articles in our index yet.