Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 16 submissions in the queue.
posted by Fnord666 on Thursday December 20 2018, @11:31AM   Printer-friendly
from the people-still-use-IE? dept.

Submitted via IRC for Bytram

Microsoft delivers emergency patch for under-attack IE

Microsoft rarely mentions Internet Explorer (IE) anymore, but when it does, it usually means bad news.

So it was Wednesday, when Microsoft issued a rare emergency security update to plug a critical vulnerability in the still-supported IE9, IE10 and IE11. The flaw was reported to Microsoft by Google security engineer Clement Lecigne.

According to Microsoft, attackers are already exploiting the vulnerability, making it a classic "zero-day" bug. Because of that, the company released a fix before the next round of security updates scheduled for Jan. 8.

The update was issued to Windows 7, 8.1 and 10 - the latter with patches for versions 1607 and later - as well as Windows Server 2008, 2012, 2016 and 2019. (Updates for some versions of Windows 10 - 1607 and 1703 - were available only to Windows 10 Enterprise and Windows 10 Education.)

"A remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Internet Explorer," Microsoft stated in the CVE-2018-8653 support document. "The vulnerability could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user."

The vulnerability could be exploited simply by drawing users running IE9, IE10 or IE11 to a malicious website, perhaps with a phishing email.

[...] The IE security fix will be automatically offered, downloaded and installed on most unmanaged Windows PCs.


Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
(1)
  • (Score: 2) by looorg on Thursday December 20 2018, @01:06PM (4 children)

    by looorg (578) on Thursday December 20 2018, @01:06PM (#776782)

    Microsoft rarely mentions Internet Explorer (IE) anymore, but when it does, it usually means bad news.

    Was there really a time when IE wasn't bad news? I can't recall ever hearing someone praise IE for it being good. Not even when it was brand spanking new, it was then still inferior to Netscape Navigator etc.

    • (Score: 3, Funny) by Runaway1956 on Thursday December 20 2018, @03:18PM (1 child)

      by Runaway1956 (2926) Subscriber Badge on Thursday December 20 2018, @03:18PM (#776808) Journal

      found a script to download and install Arch Linux over the Windows install.

      • (Score: 3, Funny) by ElizabethGreene on Thursday December 20 2018, @03:26PM

        by ElizabethGreene (6748) Subscriber Badge on Thursday December 20 2018, @03:26PM (#776814) Journal

        You did? Check your IDA settings, as you should have found a routine that adds bounds checking to some of the routines in our legacy ECMAScript provider, Jscript.dll.

    • (Score: 1) by EEMac on Thursday December 20 2018, @03:34PM

      by EEMac (6423) on Thursday December 20 2018, @03:34PM (#776816)

      Back in the Visual Basic days, IE supported ActiveX. ActiveX let you do some very sophisticated stuff that HTML wasn't yet ready for. IE is bad news now - and ActiveX was always bad for security - but for a few years it let you do things other browsers couldn't.

    • (Score: 2) by All Your Lawn Are Belong To Us on Thursday December 20 2018, @03:59PM

      by All Your Lawn Are Belong To Us (6553) on Thursday December 20 2018, @03:59PM (#776820) Journal

      The day they released Edge upon the world.

      --
      This sig for rent.
  • (Score: 0) by Anonymous Coward on Thursday December 20 2018, @04:34PM (3 children)

    by Anonymous Coward on Thursday December 20 2018, @04:34PM (#776828)

    Are we talking JavaScript here? (or ECMAscript or M$ bastard JScript)

    • (Score: 3, Informative) by ElizabethGreene on Thursday December 20 2018, @06:13PM (2 children)

      by ElizabethGreene (6748) Subscriber Badge on Thursday December 20 2018, @06:13PM (#776883) Journal

      Are we talking JavaScript here? (or ECMAscript or M$ bastard JScript)

      Yes and no. The effected binary is Jscript.dll which is not the default javascript engine in IE 10 and 11. The default engine in those is Jscript9.dll. The old engine can be used by a modern browser under certain circumstances.

      I assume those circumstances include explicitly asking for it and/or compatibility rendering scenarios, but I haven't been able to demonstrate that to my satisfaction yet.

      • (Score: 3, Funny) by ElizabethGreene on Friday December 21 2018, @12:24AM (1 child)

        by ElizabethGreene (6748) Subscriber Badge on Friday December 21 2018, @12:24AM (#777023) Journal

        Apologies for failing to mention this earlier; I'm a Microsoft Platforms PFE supporting enterprise customers.

        • Please don't hold that against me.
        • Yes I know that makes my opinion invalid.
        • The only extinguishing I'll be doing is if one of us is on fire.
        • (Score: 0) by Anonymous Coward on Friday December 21 2018, @09:35AM

          by Anonymous Coward on Friday December 21 2018, @09:35AM (#777149)

          Thanks for the useful insider reply and sorry to hear of your predicament.

(1)