Apple's latest software updates fix flaw resembling Android Stagefright
Apple's recent iOS, OS X, tvOS and watchOS updates patch a previously unknown security flaw that allows the surreptitious gathering of sensitive data with a simple text message, an OS-level bug which bears a striking resemblance to last year's much derided Stagefright exploit on Google's Android platform.
Like Stagefright, the iOS vulnerability discovered by Cisco Talos engineer Tyler Bohan involves media files delivered by MMS, specifically specially crafted Tagged Image File Format (TIFF) files that contain nefarious payloads used to trigger buffer overflows.
As described by Bohan, when an infected TIFF file is opened on a target device it triggers a buffer overflow in iMessage, or any other app using Apple's Image I/O API to render the image, allowing for remote code execution. Depending on the malicious file's instruction set, nefarious users might be able to gain access to account logins, passwords and other sensitive information.
Bohan notes the vulnerability is especially dangerous as certain iOS apps, including iMessage, automatically attempt to render TIFF images by default. In such cases, payloads would trigger themselves without user intervention. Safari is also vulnerable, though users need to click on a link or load a malicious webpage to trigger the payload.
Forbes reported on the vulnerability's discovery earlier today.
According to Apple's website, the patched flaw impacts image data handler ImageIO, meaning hardware running older versions of iOS, OS X, tvOS and watchOS are at risk. Luckily, Apple on Monday released iOS 9.3.3, OS X 10.11.6, tvOS 9.2.2 and watchOS 2.2.2, all of which patch the bug.
Like Stagefright, the iOS vulnerability discovered by Cisco Talos engineer Tyler Bohan involves media files delivered by MMS, specifically specially crafted Tagged Image File Format (TIFF) files that contain nefarious payloads used to trigger buffer overflows.
As described by Bohan, when an infected TIFF file is opened on a target device it triggers a buffer overflow in iMessage, or any other app using Apple's Image I/O API to render the image, allowing for remote code execution. Depending on the malicious file's instruction set, nefarious users might be able to gain access to account logins, passwords and other sensitive information.
Bohan notes the vulnerability is especially dangerous as certain iOS apps, including iMessage, automatically attempt to render TIFF images by default. In such cases, payloads would trigger themselves without user intervention. Safari is also vulnerable, though users need to click on a link or load a malicious webpage to trigger the payload.
Forbes reported on the vulnerability's discovery earlier today.
According to Apple's website, the patched flaw impacts image data handler ImageIO, meaning hardware running older versions of iOS, OS X, tvOS and watchOS are at risk. Luckily, Apple on Monday released iOS 9.3.3, OS X 10.11.6, tvOS 9.2.2 and watchOS 2.2.2, all of which patch the bug.
Comments
Stagefright is one of the biggest reasons why I defend iOS. Tell me it isn't the same only "similar" in a clickbait manner.
Can it be triggered without opening a message like StageFright?
The 1st point is serious because it means that the number of infected users will continue to grow overtime, despite efforts by Google/partners.
The 2nd point is serious as it drew significant attention to the vulnerability and how it worked - enabling many more nefarious actors to implement it
The 3rd point is serious because, unlike iOS, there was a demonstrable outcome to the vulnerability. This is different from iOS as the payload may not have been able to be effective due to other layers of iOS security coming into play (which has significantly limited the scope for damage with other iOS vulnerabilities in the past.)
Unlike Android, this is not iOS's first day at the rodeo.
The "passwords" thing only applied to Safari crashing when displaying the TIFF and it only had access to data in MobileSafari's address space (or APIs Safari had access to that didn't require XPC service privilege checks). This pretty much limited it to cookies and any websites you had visited with login forms visited during that Safari session (iOS frequently tombstones Safari in the background, which purges this memory).
Either way, it was announced after Apple had pushed out the update that fixed it.
There's been other security patches since then that address other discovered flaws as Google is on a regular monthly schedule of security fixes as of last year, and all are sent to OEM's as well. Thank the Stagefright scare for that. Some of those OEM's even roll those patches out to users devices quickly too! (ie Blackberry, Sony, some Samsung and LG smartphones among others). No idea how long Apple took with theirs as it wasn't publicly disclosed until now, so it could be a matter of days or a matter of weeks.
As with Android the Apple iOS security hole has been there for a long time, just that no one (we assume) had found it.