The May 2017 Apple Security Update Review

Others may be looking deeply into the latest ransomware attack, but while that is occurring, the regularly scheduled updates continue. As we did earlier with Adobe and Microsoft updates, let’s take a closer look at the latest security releases from Apple for the month of May 2017.

Many of the bugs patched with these updates should be considered critical as they could allow remote code execution. As with many Apple updates, CVEs are spread across multiple patches. To help better visualize which CVEs are attached to which products, refer to the following table:

· macOS Sierra 10.12.5: Security Update 2017-002 El Capitan and Security Update 2017-002 Yosemite address 37 different CVEs. Included are several bug fixes in the kernel, which will likely require a restart once applied. Several of these issues – primarily sandbox escapes – were initially disclosed during the Pwn2Own contest earlier this year.

· iOS 10.3.2: This release addresses 41 total CVEs. The update includes several different fixes for WebKit, which of course also show up in the Safari update too. The most severe of these bugs could allow the processing of maliciously crafted web content to allow arbitrary code execution. Also included in the iOS fixes are updates to the certificate trust policy. According to the write-up, there was a validation issue in the handling of untrusted certificates. Similar issues on other platforms allowed malware to appear as legitimate software.

· watchOS 3.2.2: This addresses 12 different CVEs. All of these CVEs are shared with either the iOS update, the macOS update, or both. There are a few shared with tvOS, as well.

· tvOS 10.2.1: The patch addresses 23 CVEs. As with the watchOS update, there are no unique CVEs fixed by this patch. In addition to sharing bugs with the other OSes, the tvOS also has CVEs in common with the patch for Safari.

· Safari 10.1.1: While fixing 26 CVEs, this patch is similar to what is seen in the iOS update, the most severe issues are WebKit bugs that could allow remote code execution.

And yes – these patches address a majority of the issues disclosed during the most recent Pwn2Own contest.

Apple doesn’t disclose if any of these issues are publicly known or under active attack, but as recently highlighted by real-world events, patching matters. It may not be the easiest task – especially when patches release with little fanfare. However, the consequences of not applying these updates could prove costly in the months to come.