"No way to prevent this" say users of only language where this regularly happens
Published on , 287 words, 2 minutes to read
In the hours following the release of OVE-20240719-0001 for the project CrowdStrike Falcon, site reliability workers
and systems administrators scrambled to desperately rebuild and patch all their systems to fix a bootloop where systems will get hit with PAGE_FAULT_IN_NONPAGED_AREA. This has taken out hospitals, major banks, Microsoft Azure, Sky News, Berlin-Brandenburg airport, and basically every major enterprise deployment of Windows. This is likely going to take days for some customers to recover from due to the fact that they need to do manual workarounds with remote hands to get systems to even boot. Reportedly there is at least one hospital that had their entire health system go down during a heart attack surgery.
This is due to the affected components being written in C++, the only programming language where these vulnerabilities regularly happen. "This was a terrible tragedy, but sometimes
these things just happen and there's nothing anyone can do to stop them," said programmer Prof. Mortimer Wuckert, echoing statements
expressed by hundreds of thousands of programmers who use the only language where 90% of the world's memory safety vulnerabilities have
occurred in the last 50 years, and whose projects are 20 times more likely to have security vulnerabilities. "It's a shame, but what can
we do? There really isn't anything we can do to prevent memory safety vulnerabilities from happening if the programmer doesn't want to
write their code in a robust manner." At press time, users of the only programming language in the world where these vulnerabilities
regularly happen once or twice per quarter for the last eight years were referring to themselves and their situation as "helpless."
Facts and circumstances may have changed since publication. Please contact me before jumping to conclusions if something seems wrong or unclear.
Tags: