Division by zero bug found in FFmpeg with a vibecoded fuzzer

https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/24290

62 points · 7 comments · view on lemmy.world

7 Comments

Ch3rry314@piefed.social · 41 pts · 5d (7 replies)

Am 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.

Brownboy13@lemmy.world · 9 pts · 5d (1 reply)

This fuzzer doesn't seem to be an AI/LLM based tool.

technocrit@lemmy.dbzer0.com · 7 pts · 5d

No bug discovered. No "vibecoding" detected.

Gotta love tech "journalism".

sxh3mr@discuss.tchncs.de · 6 pts · 5d

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

plateee@piefed.social · 5 pts · 5d (2 replies)

In theory they can "find" new things, but typically it's based on other training data.

Reality@feddit.org · 1 pts · 5d (1 reply)

Do you mean LLMs can find new bug classes or new bugs?

plateee@piefed.social · 4 pts · 5d

New bugs, not bug classes.

They also seem to do well with chaining low severity vulnerabilities to result in an overall high severity exploit.

morto@piefed.social · 1 pts · 5d
[ removed ]