Wouldn't a strongly typed language like rust sill catch a bad datafile?
E.g. loading it would require you to setup a maximal size and a valid configuration struct?
E.g. loading it would require you to setup a maximal size and a valid configuration struct?
We haven't seen the code but it could be something like:
char *ptr = parsefile(file_we_released_without_testing);
if(ptr[0]=='A') { } // BSOD loop
So this style of error can be addressed by using a safe language. Or static analysis. Or code reviews. Or not doing this stuff in the kernel. Or formal methods. Or fuzzing.
As someone else said you likely can't easily use Rust for Windows kernel modules/drivers. I'm sure a strong enough engineering team could do it (e.g. transpile Rust to C) but I'm not sure it's the biggest engineering problem CrowdStrike has. Microsoft has a complete tool-chain for developing these and it's usually C/C++ or assembly.
func parsefile(string) string {
}
func thatfunctionthatcrashedinC() {
defer func() {
if err := recover(); err != nil {
log.Println("panic occurred:", err)
}
}()
result := parsefile(badfilethatcrashesC);
if result[0] == 'A' {
}
}