New answers tagged

0

It's pointless to look for system calls in the code of a kernel driver. Kernel code is what system calls call. A kernel module has exactly the same privileges as the part of the kernel that's loaded at boot time. There is no memory protection inside the kernel. The Linux kernel contains some protection against accidental errors in kernel modules: for example ...


1

Trusting kernel drivers is bad. Oh? Why? Almost everybody does this. Whether it is a Windows kernel driver or a Linux driver doesn't matter. Furthermore: they are an extension of the kernel, and if you don't trust device drivers, why trust the rest of the kernel? In general, we trust the OS we get. We take some precautions to make sure it is correct (for ...


1

Now if this firmware is somehow hacked or infected and if you take it to another PC, is it possible for this firmware to infect other hardware on this new PC? Yes, certainly. This could be done by supplying a custom boot sequence, or supplying altered information to the boot process (the malware does not need to integrate in the boot process: it can boot ...


0

The issue was because I was not spawning a cmd.exe process via _popen or system post shellcode execution.


Top 50 recent answers are included