[Swordmaker]

Please note, this is NOT a zero day exploit, as claimed nor was it discovered by researchers because it was unknown to Apple. It requires FIVE different things to happen for it to be an exploit, and the only reason that anyone knows about it is that Apple PATCHED these vulnerabilities last week! One thing that this article fails to mention that the final thing is a Heap Buffer Overflow problem, but on both Macs and iOS devices the heaps are hardware Non-Executable memory areas, so such a heap overflow could never be exploited. At worst, it would result in an error message and the crash of an App.

All anyone has to do to avoid any malicious result of these vulnerabilities is to run a fully up-to-date version of iOS 9.3.3 or OS X.11.6 El Caplitan.

[Swordmaker]

Apple patched some vulnerabilities in both iOS and OS X which a security company is now claiming could, if used in concert, have been used to exploit both operating systems. . . but that really is not true because the final step relies on a Heap Buffer Overflow which is actually a hardware locked out, protected non-executable memory area in both systems and cannot be used to execute code, regardless of an overflow or not. Since Apple has already fixed everyone of these vulnerabilities LAST WEEK, the way to avoid ever running into even the potential for a problem is to be running up-to-date versions of iOS 9.3.3 and OS X.11.6 El Capitan. Update now. Since this is not a problem, this article is mostly FUD. — PING!

Keeping Your Apple Devices Secure
By Keeping The Up-To-Date
Ping!

The latest Apple/Mac/iOS Pings can be found by searching Keyword "ApplePingList" on FreeRepublic's Search.

If you want on or off the Mac Ping List, Freepmail me

[CodeToad]

These buffer type problems are extremely difficult to ever get to execute with current processors as current processors will not execute code located in data segments.

[Nuc 1.1]

Thanks for the info. Updated my iPad.