Re:Windows Bluescreen and Boot Loops (update: caused by a Cr...
by JackSlateur on Friday July 19, 2024 @06:52AM
(#41004789)
This is wrong, there are many facilities that, once applied, cannot be modified (unless reboot)
[ Parent
| on HN ]
Re:Windows Bluescreen and Boot Loops (update: caused by a Cr...
by lucasRW on Friday July 19, 2024 @08:44AM
(#41005919)
Such as ?
Re:Windows Bluescreen and Boot Loops (update: caused by a Cr...
by JackSlateur on Saturday July 20, 2024 @05:44AM
(#41015275)
Random example: https://man.openbsd.org/OpenBSD-7.3/msyscall
This is a syscall used by userspace to tell the kernel which memory portion is allowed to do syscalls
This syscall can only be used once : once the linker has done it, the kernel will refuse extra calls (so allowing more memory pages is not possible)
Re:Windows Bluescreen and Boot Loops (update: caused by a Cr...
by lucasRW on Tuesday July 23, 2024 @06:11PM
(#41051511)
First, we were talking about EDR in Windows usermode.
Second, still, that doesn't change anything. You can make your malware jmp to anywhere so that the syscall actually comes from an authorized page.
In fact, in windows environment, this is actively done ("indirect syscalls"), because indeed, having a random executable directly calling syscalls is a clear indicator that something is malicious. So they take a detour and have a legitimate piece of code (in ntdll) do the syscall for them.