3 ms·
> That does not impact their business or their operations in any way whatsoever. I don't know what tools and backends they use exactly, but working purely by s
by jeroenhd 1y ago
> That does not impact their business or their operations in any way whatsoever.
I don't know what tools and backends they use exactly, but working purely by statistics, I'm sure some place in Google's massive cloud compute empire is relying on ffmpeg to process data from the internet.
- themafia 1y agoAnd they're processing old LucasArts codec videos with it? Which is the specific bug report in question.
- inkysigma 1y agoIt's unlikely the specific codec that is the issue but the bug report suggests that the code path could be hit by a maliciously crafted payload since ffmpeg does file fuzzing. They almost certainly have ffmpeg stuff that touches user submitted videos.
- jeroenhd 1y agoThey're probably not manually selecting which codecs and codec parameters to accept and sticking to the default ones instead. Plus, this bug was reported by AI, so it was as much a proof of concept/experiment/demonstration of their AI security scanner as it was an attempt to help secure ffmpeg