PCs Became MORE INSECURE By Fixing Windows 7 Meltdown

Security fixes of January and February for Microsoft Intel’s Meltdown processor flaw released up an even inferior security flaw on Windows 7 PCs and Server 2008 R2 boxes. The researcher Ulf Frisk, who formerly set up evident deficiencies in Apple’s FileVault disk encryption system.

The initial Meltdown patches for 64-bit Windows 7 and Server 2008 R2 left a serious kernel memory table decipherable and writable for standard user methods. This, in turn, resources any malware on those susceptible machines, or any logged-in user, can work the operating system’s memory plan, improve administrator-level rights, and excerpt and adjust any facts in RAM.

Meltdown chip-level flaw lets harmful software, or deceitful logged-in users, on a recent Intel-powered machine to deliver passwords, private information, and other confidential from saved kernel memory. But the security patches from Microsoft for the flaw, on Windows 7 and Server 2008 R2, give out in January and February, finished up conceding usual programs read and write access to all of physical memory. Frisk supported up his privilege with a comprehensive collapse and a proof-of-concept abuse, the issue boils down to a sole bit fortuitously agreed by the kernel in a CPU page table access. This moment allowed read-write user-mode acquire to the top-level page table itself.

So it can continuously be found and altered by activity code on Windows 7 and Server 2008 that PML4 table is at a patched address. With that major approval bit flicked from supervisor-only to any-user, the table let entire processes to alter stated table, and therefore tweak up and write to memory addresses they are not thought to extent.

Microsoft’s programmers unintentionally left the top-level table clear entirely open for user-mode programs to change, letting them to rephrase the computer’s manual of memory mappings. Letting it distinguish where memory is situated and what can acquire it consider such tables as a telephone directory for the CPU.

“Windows 7 already did the hard work of mapping in the required memory into every running process,” Frisk explained. “Exploitation was just a matter of read and write to already mapped in-process virtual memory. No fancy APIs or syscalls required – just standard read and write!”

Windows 8.x and Windows 10 are not all affected. The recent updates include a patch that addresses this approval bit cockup for influenced versions. Microsoft did not answered to a demand for comment on the problem. In brief, fix your Windows 7 and Server 2008 R2 machines with the updated security info to defend against this OS venerability, or else any methods or users can interfere with and take away data from physical RAM, and offer themselves admin-level switch. It never appear any of the Meltdown patches and let programs to read from kernel memory.

Leave a Reply

Your email address will not be published. Required fields are marked *