Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> By crafting a malicious JPEG/PNG that specified inflated dimensions, an attacker could cause the decoders to allocate an overly large buffer to hold the decoded pixel data. When copying pixel data from the file into the buffer, the attacker could overflow the bounds of the buffer and overwrite adjacent memory.

This is such a trivial exploit, why in the world they decided to write an own JPEG decoder, and stumble on the seemingly most trivial case of input sanitation?

I would add sole reliance on sandboxing instead of principial stance on writing on overall secure, high quality, and higly verified codebase is obviously failing.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: