This site may earn affiliate commissions from the links on this page. Terms of use.

win7 melt

Security circles were thrown into disarray tardily last year when serious bugs known every bit Meltdown and Spectre threatened to leak private data from computers around the world. The industry spent months developing patches while the public remained unaware of the danger. Updates only began rolling out early this twelvemonth, and many of them have been buggy or downright broken. In fact, it sounds like Microsoft's Meltdown patch didn't fifty-fifty make Windows 7 more secure. Information technology actually did the opposite.

Meltdown and Spectre are then dangerous because they affect one of the most of import depression-level features of CPUs known every bit speculative execution. That's a process by which a processor can perform calculations you are likely to need before beingness instructed to do so. The result is improved organisation responsiveness. Still, Meltdown and Spectre can allow a rogue process to accept advantage of speculative execution and read all active memory, including sensitive data like passwords.

These vulnerabilities afflicted most modern CPU designs, particularly Intel's chips. Microsoft has to deal with virtually all CPU architectures, and so its patches are particularly important. Swedish security researcher Ulf Frisk reports that Microsoft's patch for Meltdown doesn't prevent data leakage on Windows 7. Information technology actually accelerated the procedure of reading secure information instead. Originally, Meltdown could permit a process to read memory at a charge per unit of 120Kbps, only that increased to multiple gigabits per 2d after the patch.

According to Frisk, the new flaw affects virtually versions of Windows 7 and Server 2008 R2. The issues stem from a single scrap in the kernel page tables memory translator that controls access permissions for kernel retentivity. That scrap was accidentally flipped from supervisor-only to any user. Thus, all users of a system have unfettered access to the kernel folio tables, only information technology should but exist accessible to the kernel.

Frisk created a proof-of-concept exploit, which runs on 64-fleck versions of Windows vii and Server 2008 R2. The PLM4 page table is in a fixed retention location, so no "fancy" tricks are needed to utilize the Meltdown attack. Later on gaining read-write access, you lot tin read all the physical memory at a much faster rate than before the patch.

A fix for the exploit in the last patch has already been adult. Microsoft began rolling information technology out on Tuesday. All users of Window seven or Server 2008 R2 should manually run the update checker if they haven't already. Hopefully, this is the terminal do-over Microsoft volition need to get these exploits blocked.