On Tuesday August 18, 2015, Microsoft published an advisory pointing out a 0-day vulnerability (CVE-2015-2502) that can be exploited by an attacker to perform a remote code execution on Internet Explorer (from version 7 to 11, even if you are running Windows 10) web browser allowing him to gain the same user rights as the current user. The vulnerability resides in how IE handles objects.
These last days, I have been diving into this vulnerability to understand it so I landed on Understanding and Solving Internet Explorer Leak Patterns where I got quite an interesting insight on how IE object handling has always suffering from different bugs which are grouped by Microsoft into 4 categories (Circular References, Closures, Cross-Page Leaks and Pseudo-Leaks).
Since the causes of these memory leaks are caused by the way JavaScript, DOM ... are interacting in IE, could these memories leaks be common to Firefox and Chrome or are they specifically inherent to IE?