Post
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.
0 reposts3 likes
I have seriously considered writing a memory-safe Zstandard decompressor because otherwise a single bad upstream zstd bug could spell RCE for tens of thousands of my app users. Decompression libraries are the most significant reason I sandboxed Ina for Accrescent. lberrymage.dev/posts/ina-pa...