Slashdot Mirror


Windows 8 and Later Fail To Properly Apply ASLR (bleepingcomputer.com)

An anonymous reader writes: Windows 8, Windows 8.1, and subsequent Windows 10 variations fail to properly apply ASLR, rendering this crucial Windows security feature useless. The bug appeared when Microsoft changed a registry value in Windows 8 and occurs only in certain ASLR configuration modes. Basically, if users have enabled system-wide ASLR protection turned on, a bug in ASLR's implementation on Windows 8 and later will not generate enough entropy (random data) to start application binaries in random memory locations. For ASLR to work properly, users must configure it to work in a system-wide bottom-up mode. An official patch from Microsoft is not available yet, but a registry hack can be applied to make sure ASLR starts in the correct mode.

The bug was discovered by CERT vulnerability analyst Will Dormann while investigating a 17-years-old bug in the Microsoft Office equation editor, to which Microsoft appears to have lost the source code and needed to patch it manually.

3 of 62 comments (clear)

  1. Summary fail by Harold+Halloway · · Score: 4, Informative

    WTF is 'ASLR?'

    1. Re:Summary fail by freeze128 · · Score: 5, Informative

      Address Space Layout Randomization - A security feature that prevents a certain type of exploit that would jump to a known location in ram to run a subroutine. If code was loaded in random locations, the exploit would not be successful.

    2. Re:Summary fail by rickb928 · · Score: 4, Informative

      It is a best practice to spell out the meaning an acronym when first introduced in a document. I work in a complex corporate environment, and acronyms such as BCP, CEN, RFP, COP, and a host of others mean different things in different contexts. If I get new ones, like CTH, HDT, and IDN regularly, and these happen to mean different things. Stating the meaning up front, and then repeating it as the audience expands, is helpful to many who just don't get out enough.

      And most of the authors are oblivious to the crossovers. I work with a lit of different teams, at different levels, and get exposed to a huge swath of the organization, with all the joyous bleed of functions and ownership that goes with that. Writing for a diverse audience is a challenge.

      FWIW, that acronym is so common here I feel confident I can violate my own style rules, but someone won't readily recognize it. Darn.

      --
      deleting the extra space after periods so i can stay relevant, yeah.