CVE-2016-1818: Buffer Overflow
First published: Fri May 20 2016(Updated: )
IOAcceleratorFamily in Apple iOS before 9.3.2, OS X before 10.11.5, tvOS before 9.2.1, and watchOS before 2.2.1 allows attackers to execute arbitrary code in a privileged context or cause a denial of service (memory corruption) via a crafted app, a different vulnerability than CVE-2016-1817 and CVE-2016-1819.
Credit: product-security@apple.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apple iOS and macOS | <=10.11.4 | |
| iStyle @cosme iPhone OS | <=9.3.1 | |
| Apple iOS, iPadOS, and watchOS | <=2.2 | |
| tvOS | <=9.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://lists.apple.com/archives/security-announce/2016/May/msg00001.html
- http://lists.apple.com/archives/security-announce/2016/May/msg00002.html
- http://lists.apple.com/archives/security-announce/2016/May/msg00003.html
- http://lists.apple.com/archives/security-announce/2016/May/msg00004.html
- http://www.securityfocus.com/bid/90694
- http://www.securitytracker.com/id/1035890
- http://www.zerodayinitiative.com/advisories/ZDI-16-637
- https://support.apple.com/HT206564
- https://support.apple.com/HT206566
- https://support.apple.com/HT206567
- https://support.apple.com/HT206568
Frequently Asked Questions
What is the severity of CVE-2016-1818?
CVE-2016-1818 has a high severity rating due to its potential to allow arbitrary code execution.
How do I fix CVE-2016-1818?
To fix CVE-2016-1818, ensure that your operating system is updated to at least iOS 9.3.2, macOS 10.11.5, tvOS 9.2.1, or watchOS 2.2.1.
Which versions of Apple software are affected by CVE-2016-1818?
CVE-2016-1818 affects Apple iOS versions prior to 9.3.2, OS X versions before 10.11.5, tvOS versions before 9.2.1, and watchOS versions before 2.2.1.
What types of attacks can CVE-2016-1818 enable?
CVE-2016-1818 can enable attacks that lead to arbitrary code execution and denial of service due to memory corruption.
Is there a workaround for CVE-2016-1818?
There is no official workaround for CVE-2016-1818; updating to the latest versions is the recommended approach.
- agent/type
- agent/weakness
- agent/severity
- agent/references
- agent/author
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/apple
- canonical/apple ios and macos
- version/apple ios and macos/10.11.4
- canonical/istyle @cosme iphone os
- version/istyle @cosme iphone os/9.3.1
- canonical/apple ios, ipados, and watchos
- version/apple ios, ipados, and watchos/2.2
- canonical/tvos
- version/tvos/9.2