Null pointer dereference is a crash, not a security bug
Null pointer dereference is a crash, not a security bug
Posted Nov 5, 2007 15:26 UTC (Mon) by mheily (guest, #27123)In reply to: Thanks for proving Bernstein right by man_ls
Parent article: Daniel Bernstein: ten years of qmail security
> Ehm, my C is a little rusty, but no :D I rather meant null pointer dereference, double dereference or whatever other strange things are allowed in C that lead to security problems. If a program attempts to dereference a NULL pointer, the program will be terminated immediately with a SIGSEGV signal. This does not allow arbitrary code to be executed. A double dereference is a perfectly normal and desirable condition in many programs, and the compiler will catch double-vs-single pointer mismatches at compile time. > Of course not, but I much rather prefer a NullPointerException than an undesired intrusion. Again, there is no way for a NULL pointer dereference to facilitate an intrusion since the program will segfault instead of executing arbitrary code.
