https://multimedia.cx/eggs/googles-youtube-uses-ffmpeg/
It wouldn't be too surprising if they still did.
https://multimedia.cx/eggs/googles-youtube-uses-ffmpeg/
It wouldn't be too surprising if they still did.
But the ffmpeg processes are surely sandboxed with seccomp or similar, so it probably does not matter at all.
(quite likely, those are all actually virtual through some auto-scaling IaaS magic)
Literally the hacker would upload a video, wait for it to encode, and then once it was available for viewing on the website, they'd be looking at a video containing the text from `/etc/passwd` or your envvars or some secrets file or whatever.
Yes, most encoding services are very well-sandboxed and even when our tiny streaming platform at the time got hit by this when it was first appeared a few years ago, it was a non-issue because there was nothing valuable or compromising on the encode servers for them to read. (I think Ubuntu AppArmor stopped it dead in its tracks on its own, anyway.)
[0] https://docs.google.com/presentation/d/1yqWy_aE3dQNXAhW8kxMx...