3 ms·

Stop weird machines! http://langsec.org/occupy/ http://langsec.org/occupy/

• tialaramex 5y ago
  In this particular case: If you are Wrangling Untrusted File Formats, you should be doing so Safely, using WUFFS. You can't make this mistake in WUFFS. Your WUFFS image decoder might decode the image incorrectly, maybe Rudolph has a green or blue nose, maybe he's upside down or just a sea of noise, but it can't have a buffer overflow even if you screwed up really badly. For example, any equivalent of the repeated addition numSyms += ((JBIG2SymbolDict *)seg)->getSize(); in WUFFS will get flagged, it clearly could overflow and WUFFS wants you to write code explaining how you're going to prevent that because overflows aren't allowed in WUFFS. This leaves outfits like NSO with nothing much to attack. Sending me pictures of Rudolph with a green nose by "exploiting" a bug in my image decoder isn't very useful, unlike taking over my phone...
  • snypher 5y ago
    https://github.com/google/wuffs https://github.com/google/wuffs
  • shp0ngle 5y ago
    the problem is, this is an ancient PDF feature from the 90s that nobody has time to write and debug so they just took an open source parser and slapped it in there it’s hard to rewrite PDF parsing to a new language so that everything still works. Especially those weird features that people forgot about.