CVE-2015-6050

Microsoft Internet Explorer 10 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka “Internet Explorer Memory Corruption Vulnerability.”

CVE-2015-6052

The Microsoft (1) VBScript 5.7 and 5.8 and (2) JScript 5.7 and 5.8 engines, as used in Internet Explorer 8 through 11 and other products, allow remote attackers to bypass the ASLR protection mechanism via a crafted web site, aka “VBScript and JScript ASLR Bypass.”

CVE-2015-6053

Microsoft Internet Explorer 11 allows remote attackers to obtain sensitive information from process memory via crafted parameters in an ArrayBuffer.slice call, aka “Internet Explorer Information Disclosure Vulnerability.”

CVE-2015-6055

The Microsoft (1) VBScript 5.7 and 5.8 and (2) JScript 5.7 and 5.8 engines, as used in Internet Explorer 8 through 11 and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted Filter arguments, aka “Scripting Engine Memory Corruption Vulnerability.”

CVE-2015-6056

The (1) JScript and (2) VBScript engines in Microsoft Internet Explorer 9 through 11 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka “Scripting Engine Memory Corruption Vulnerability.”

CVE-2015-6057

Microsoft Edge allows remote attackers to obtain sensitive information from process memory via a crafted web site, aka “Microsoft Edge Information Disclosure Vulnerability.”

CVE-2015-6058

Microsoft Edge mishandles HTML attributes in HTTP responses, which allows remote attackers to bypass a cross-site scripting (XSS) protection mechanism via unspecified vectors, aka “Microsoft Edge XSS Filter Bypass.”

CVE-2015-6059

The Microsoft (1) VBScript 5.7 and 5.8 and (2) JScript 5.7 and 5.8 engines, as used in Internet Explorer 8 through 11 and other products, allow remote attackers to obtain sensitive information from process memory via a crafted web site, aka “Scripting Engine Information Disclosure Vulnerability.”

Re: Watch your Downloads: the risk of the "auto-download" feature on Microsoft Edge and Google Chrome

Posted by Lee on Oct 13

Stefan Kanthak, everything you said is true but from the point of view
of an enterprise with controlled user accounts. A home user uses the
default administrator account the manufacturer added to MS Windows.
For someone that installed MS Windows themselves, they use the default
administrator account the MS Windows installer helped them create.
Then when they run into something not working how they want, they read
the first post online about how…

Re: Watch your Downloads: the risk of the "auto-download" feature on Microsoft Edge and Google Chrome

Posted by Stefan Kanthak on Oct 13

Lee “who still doesnt use his full name” <curtlee2002 () gmail com> wrote:

Thanks. But I knew this already.-P

Windows operates the same way in an enterprise and at home: its
loader searches DLLs and EXEs which are referenced with just their
simple filename instead of their absolute pathname in the “application
directory” first.
See <https://msdn.microsoft.com/en-us/library/ms682586.aspx>
and <…