18 ms·
This is not a real bug in FFmpeg. This is a demonstration that if you control a custom AVIO module it is possible to crash FFmpeg by giving it bad data.
by cptroot 22d ago
This is not a real bug in FFmpeg. This is a demonstration that if you control a custom AVIO module it is possible to crash FFmpeg by giving it bad data.
- inigyou 22d agoNot custom. It's an existing module for a format called VPK. It's a quite trivial bug though, not exploitable apart from DOS and won't ever happen in a real file.
- VladVladikoff 22d agoI even question if it is a DOS vector. So the thread crashes and then the system that controls the threads cleans it up and opens a new thread. Seems to be a trivial impact, unless it locks up the thread somehow.
- inigyou 22d agoThreads don't work that way. A fatal exception on any thread kills the process.
- VladVladikoff 22d agoAnd the parent will spawn a new process. Unless the server is terribly poorly misconfigured. Edit; for what it’s worth I’ve run a server processing video with FFMPEG for 10 years now, and there’s just so many things that can make FFMPEG crash. All sorts of corrupted videos people upload. If your server doesn’t recovery gracefully from a crashed FFMPEG thread, that’s on you, not FFMPEG.
- LoganDark 22d agoI thought you meant Disk Operating System until I realized you probably meant DoS
- avadodin 21d agoFFmpeg on DOS is enough for anybody as long as you let your 0.00066B model check the movie for 0day exploits.