Virtual Machines and Memory Protections
Posted Nov 22, 2006 19:28 UTC (Wed) by bluefoxicy
In reply to: Virtual Machines and Memory Protections
Parent article: Virtual Machines and Memory Protections
Exactly what the article is about. Once the JIT compiler is allowed to do such things, it's a free-for-all. They call mmap() or mprotect(), which goes into glibc, which means the kernel doesn't know who's doing what. If you happen to have exploitable code from some native library that makes up the JIT or that's called from C# code, you're allowing that native library the same permissions.
to post comments)