Post

For something so commonly used to parse complex, untrusted data (decompression), I wish we would seriously consider as an industry creating memory-safe implementations and sandboxing this code

Unfortunately, there are often tradeoffs of lower portability (Rust), less straightforward APIs (sandboxing), and/or lower performance (managed languages). But some of us are willing to make those tradeoffs.

Dropbox did this right I think. They wrote a brotli decompressor in a memory-safe langauge and sandboxed it. Granted, it takes effort to support platform-specific sandboxing capabilities, but isn't that worth the protection from vulnerabilities like these? dropbox.tech/infrastructu...

My opinion is that unless memory safe implementations and sandboxing become defaults directly in consumer libraries, the overall issue won't significantly improve. Developers shouldn't need to know that "if this ZIP library has a bug, a bad file could hack my machine." It's not intuitive.