Discussion
I am not seeing anyone reporting one big moral of this week's CVEpocalypse story:
deprecate the C programming language, like we should have done 30+ years ago.
time to migrate that shit.
though I guess no one has time for that, so now we all just have to stew in it. 
I assure you, adding more C LOC will NOT fix the problem.
dog, the PHP fix is a sprawling 13k LOC mess of error handling, goto, and C macros.
Ada will just throw Storage_Error on OOM and crash, unless you handle the exception:
https://ada-lang.io/docs/arm/AA-11/AA-11.1/#p6_5
remember, crashing is better than the alternative. C just carries on and reads stale memory and does other weird undefined behavior to enable RCE on 70% of the Web.
since most people are not familiar with Ada, I should add that it provides facilities for creating your own storage (sub-)pools:
https://ada-lang.io/docs/arm/AA-13/AA-13.11
used to great effect by the ParaSail language, written in Ada:
from parasail-lang.org:
> eliminates a global garbage-collected heap – automatic storage management is provided using region-based storage management which provides immediate, automatic reclamation of storage with none of the global contention and disruption associated with a global garbage-collected heap;
Install Fedizen
Get the full app experience
@theruran "though I guess no one has time for that, so now we all just have to stew in it."
Ah, but what if… I could sell you a machine that uses global warming to turn C into untrustworthy, unreadable, but memory-safe Rust? Unless my machine decides to randomly emit a "unsafe" symbol, then it becomes memory-unsafe Rust