5 ms·
Do also note that re-encoding can also be used as part of the exploit. E.g. Team Fortress 2 recently had one that exploited a similar system.
by hju22_-3 2y ago
Do also note that re-encoding can also be used as part of the exploit. E.g. Team Fortress 2 recently had one that exploited a similar system.
- toast0 2y agoThere'a been explpots in image, video, and audio codecs... Which is why it's important to protect your users, but also your servers... Best to sandbox/jail/etc as tightly as possible, and limit the codecs to only what you need. You can configure the ffmpeg builds pretty granularly... default will include too much.
- beeboobaa3 2y agoI care more about protecting my servers than my users. If one user attacks another that's not really my problem, blame can easily be shifted to the browser. But if someone hacks my servers and leaks everyone's data, that's my problem. So not encoding is probably the safer way to go for the business.
- mthoms 2y agoYikes. What if the other user getting attacked is you or another admin on your team? Now the attacker has admin access and can compromise your servers and “leak everyone’s data” just fine. I don’t think you’ve thought this through.
- bawolff 2y agoTrust me, your website will always get blamed regardless of its a user fault. If websites get blamed when users reuse passwords, they are definitely getting blamed if you distribute malicious files.
- theendisney 2y agoYou can think that but you should never say or write it. :p
- beeboobaa3 2y agoIt was just a joke, your honor.
- theendisney 2y agoI got the picture.
- kevincox 2y agoI don't think the exploit in that case was re-encoding. What happened is an image with very large dimensions was uploaded. When this was decoded into a raw pixel buffer on the client it used tons of memory. It was effectively a zip bomb attack. In fact re-encoding probably would have solved this as the server could enforce the expected dimensions and rescale or reject the image.