Administrator lives in Ring 3 while this crash happens in Ring 0.
Nobody, not even Admin shouldn't be able to corrupt kernel space. It's
not a security issue per se - it's just a bug.
dale@xxxxxxxxxxx wrote:
So, let me try and understand this.
According to what you have written, and the MSDN documentation on this CreateIpForwardEntry2 call, you need to be (at least) a member of the Administrators group.
So how is this "security vulnerability" any different to me creating a program, which will require the same Administrative rights, to say, wipe the boot configuration file?
