Does nobody isolate ffmpeg and friends from their application?
I can’t imagine you’d have much fun breaking into a container that terminates the moment the original ffmpeg stops, or over-runs its max execution time…
Most are heap or stack overflows in parsers and demuxers, spanning components from the TS demuxer to the VP9 decoder. depthfirst says some already carry CVE identifiers; its writeup lists nine, CVE-2026-39210 through CVE-2026-39218, and notes the rest are fixed but not yet numbered. It also published a PoC.
Manny moderate to large open source projects are effectively being ddosed by vibe coders submitting hallucinated and non-issue bug reports sometime because claude or copilot said so. Those reports are absolutely slop, no different from anything else generative ai platforms shit out.
But sure, go off on how this particular kind of output from an LLM is somehow different from rest.
What the fuck is a zero day in the context of ffmpeg?
Its not like its a system service that you can get ingress through…
“AI found 21 bugs in massive video project” sounds like junior developer shit hungry to get some shit on their resume.
Even if it wasn’t AI slop, this wouldn’t be impressive.
FFMPEG in the command line generally has permission to access the entire non-sudo filesystem and delete files.
if you upload any image on lemmy, it goes through ffmpeg to be converted into a webp file.
now, you can feed arbitrary input to that ffmpeg process
I never thought of doing that with ffmpeg. Why ffmpeg, instead of imagmagick?
ffmpeg is on any system, has a consistent user interface for many different conversions
My understanding is that ffmpeg is the bedrock that all video streaming services use. I’m suspicious it’s a bigger deal than you think
Don’t forget various conversion services, which includes photo cloud backups.
With a competently crafted payload, you could perhaps get in via someone’s transcoding pipeline.
Does nobody isolate ffmpeg and friends from their application?
I can’t imagine you’d have much fun breaking into a container that terminates the moment the original ffmpeg stops, or over-runs its max execution time…
Sure, you’d need a second exploit to escalate from there.
ffmpeg is expected to run for extended periods of time, given its use in transcoding.
Container escapes do exist, and they have shared kernel with the host
If you’re running rootless containers, it’s less of a concern. I’m trying to move all of my public containers to podman for this reason
Tell me you know nothing about the intricacies of media playback (especially hardware accelerated), without telling me…
From the article
I imagine there are many web services around the world which use ffmpeg to handle user submitted content.
Discovering bugs is not “AI slop”.
That term refers to something the AI made. This is just product testing, where a real human then fixes it as intended.
Manny moderate to large open source projects are effectively being ddosed by vibe coders submitting hallucinated and non-issue bug reports sometime because claude or copilot said so. Those reports are absolutely slop, no different from anything else generative ai platforms shit out.
But sure, go off on how this particular kind of output from an LLM is somehow different from rest.