posted in Technology
Division by zero bug found in FFmpeg with a vibecoded fuzzer
code.ffmpeg.org/FFmpeg/FFmpeg/issues/24290posted in Technology
Division by zero bug found in FFmpeg with a vibecoded fuzzer
code.ffmpeg.org/FFmpeg/FFmpeg/issues/24290Am I reading the thread correctly? This fuzzer found a “new” issue that was already identified in 2024? This matches what I’ve heard before about GenAI reporting known errors likely because they were trained on the internet as it’s data source.
In theory they can “find” new things, but typically it’s based on other training data.
Replying to @plateee@piefed.social
Do you mean LLMs can find new bug classes or new bugs?
New bugs, not bug classes.
They also seem to do well with chaining low severity vulnerabilities to result in an overall high severity exploit.
Am I reading the thread correctly? This fuzzer found a “new” issue that was already identified in 2024?
One more case of genai just increasing the work of open source maintainers (reviewing and answering to the issue) without a benefit
Replying to @Ch3rry314@piefed.social
This fuzzer doesn’t seem to be an AI/LLM based tool.
Replying to @Brownboy13@lemmy.world
No bug discovered. No “vibecoding” detected.
Gotta love tech “journalism”.
Replying to @Ch3rry314@piefed.social
With a history like ffmpegs, it’s just very likely that fuzzer findings have already been reported once. That the fuzzer is vibecoded is kinda irrelevant