Today marks the 10th anniversary of the Heartbleed vulnerability in OpenSSL, which had the same ultimate root cause as recent XZUtils backdoor incident
The XZ Utils backdoor, discovered last week, and the Heartbleed security vulnerability ten years ago, share the same ultimate root cause. Both of them, and in fact all critical infrastructure open source projects, should be fixed with the same solution: ensure baseline funding for proper open source...
The XZ Utils backdoor, discovered last week, and the Heartbleed security vulnerability ten years ago, share the same ultimate root cause. Both of them, and in fact all critical infrastructure open source projects, should be fixed with the same solution: ensure baseline funding for proper open source maintenance.
The first one was a genuine bug, the second a malicions backdoor. The only common thing is they are both open source projects. I agree with having more oversight and funding on critical open source software, but suggesting that these two vulnerabilities are the same in some way is a bit of a stretch.
This entire post is asinine. The root cause of Heartbleed was the RFC was fucked. A German graduate student wrote and implemented an RFC, and was then reviewed by the only full time (and paid) member of the OpenSSL team. Claiming it was because it wasn’t funded is stupid on its face as Dr. Henson was paid for his review.
XZ’s problem was that the maintainer had a mental breakdown and lacking structure to vet the replacement, he handed control off to what seems like a very sophisticated attack group. Money would not have fixed one of the fundamental problems with anarchistic-style code production, which is how do you trust the people who vet the code?
That’s not hugely uncommon in the open source world. An absolutely massive amount of what makes the internet tick is someone’s passion project that became a lynchpin. Sometimes they get turned into or absorbed by big projects that have corporate like structures, or straight up consumed by a massive corporation, but small projects like a single compression library that almost never needs to change? It’s likely to stay the original author’s “pet” and that’s a huge continuity problem and social engineering target.