Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by amluto on Tuesday March 27, 2018 @05:35PM
(#16692940)
Yeesh. I didn’t know that Windows still uses the self-referential page table trick. This makes me very nervous, especially since they seem to keep it mapped in the user page tables. This seems likely to poke a big hole in ASLR if nothing else. It’s a huge target for write-what-where exploits.
[ Parent
| on HN ]
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by ryuuchin on Tuesday March 27, 2018 @07:14PM
(#16693691)
They changed it in Windows 10 (RS1 IIRC)[1].
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by caf on Tuesday March 27, 2018 @08:40PM
(#16694145)
The tl;dr is that they're still using the self-referential page table trick, however the PTE_BASE is now randomised at runtime with dynamic fixups.
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by amluto on Tuesday March 27, 2018 @08:50PM
(#16694192)
If an attacker can’t find it by probing the smallish number of choices using one of many MMU layout fixes, I’d be quite surprised.
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by caf on Tuesday March 27, 2018 @08:32PM
(#16694106)
Does this bug also imply they're not using SMAP, since otherwise any kernel access to the page tables should have tripped it?
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by caf on Thursday March 29, 2018 @01:34AM
(#16704728)
Replying to myself, I guess not, because the kernel doesn't modify the user pagetables using the user pagetables' own self-referencing entry. Rather it has the kernel %cr3 loaded and modifies them using a mapping of the user pagetables in those kernel pagetables.
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by caf on Tuesday April 03, 2018 @07:32PM
(#16750441)
..which, on further reflection, raises the question: if those page tables aren't loaded when in kernel mode, why do they even need a self-referential entry at all?
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by staticassertion on Tuesday March 27, 2018 @06:51PM
(#16693554)
> This seems likely to poke a big hole in ASLR if nothing else. It’s a huge target for write-what-where exploits.
How? Is it mapped to a static location?
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by monocasa on Tuesday March 27, 2018 @07:19PM
(#16693710)
It is in Windows 7.
Re:Windows 7 patch for Meltdown enabled arbitrary reads and ...
by staticassertion on Tuesday March 27, 2018 @07:26PM
(#16693747)
Good to know, thanks.