Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We found a division by zero bug in FFmpeg with a vibecoded fuzzer

code.ffmpeg.org

Post reply on HN
Print view View original

241–250 of 274 posts

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#241

Post by pfdietz »

written-beyond wrote: post #216

IDK seems like a bug that could've taken a human a few minutes at best to find. I found a bug in SystemD that would crash the daemon because a bad SystemD unit file configuration. That took me like 5 minutes to actually track down in the actual source code. I understand the utility of this though, I just don't see this particular bug and something that would be particularly difficult o find pre LLM era.

Bugs are always easier to find in retrospect.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#242

Post by a2ff6eeb0 »

krona wrote: post #179
a2ff6eeb0 wrote: post #163

Earlier quoted context omitted.

So you put it in a loop and tell it to find the bugs in the code it wrote. What's the issue?

This is a self confession if I ever saw one.

I absolutely do this. It works great.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#243

Post by a2ff6eeb0 »

Planktonne wrote: post #201
a2ff6eeb0 wrote: post #163

Earlier quoted context omitted.

So you put it in a loop and tell it to find the bugs in the code it wrote. What's the issue?

What value are you providing in this scenario?

Manual testing, and making sure that the AI didn't create so many bugs.

But, to the underlying question, obviously as we automate more and more of our work, of course we provide less and less value. We're heading towards a future where selling thought for money isn't going to work so well.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#245

Post by a2ff6eeb0 »

bartread wrote: post #210
j16sdiz wrote: post #207

Earlier quoted context omitted.

I am expecting a unicorn.

It's weird to me that people are pushing back on me for expecting anti-bot services to actually solve the problem they already claim to solve.

Patches welcome.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#246

Post by pfdietz »

1saadcodes wrote: post #130

I find it pretty cool that a fuzzer thrown together this way actually found a bug in ffmpeg

The thing about testing is that each time you produce a new kind of tester you have a chance to find bugs in the blind spots of the previous testing approaches. Diversity makes sense, more so than in software construction.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#247

Post by encody »

inventor7777 wrote: post #170
da_chicken wrote: post #154

Earlier quoted context omitted.

I think when people are complaining about Captcha they're complaining about yet another "pick 6-20 pictures of traffic lights/school busses/stairs/stop signs/bicycles."

Not in this case. I wish I could find the actual post, but I recall reading a post on HN recently where a majority of the commenters were claiming that when they even see a Cloudflare verification checkbox that they leave the website. This makes no sense to me as in my experience, you click the checkbox and then it verifies you without extra steps.

For me it's very strange: I'd say about 7 times out of 10 it loads the checkbox for five to ten seconds, then I check it, then it loads for another five to ten seconds, refreshes the page, shows me a second checkbox, we go through the whole song and dance again, and then it lets me in.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#248

Post by dclavijo »

pfdietz wrote: post #246
1saadcodes wrote: post #130

I find it pretty cool that a fuzzer thrown together this way actually found a bug in ffmpeg

The thing about testing is that each time you produce a new kind of tester you have a chance to find bugs in the blind spots of the previous testing approaches. Diversity makes sense, more so than in software construction.

Yeah that was my bet, escaping the local minima imposed by the current state of fuzzing. I am seeing this problem as statistical and information theory problem. Some day someone by chance will create another fuzzer that would find more bugs because of the blindspots in the previous generation including mine.

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#249

Post by phyzome »

theowaway wrote: post #168
aeyes wrote: post #91

A patch for this was submitted in April: https://lists.ffmpeg.org/archives/list/ffmpeg-devel@ffmpeg.o... Edit: And there was discussion about this back in 2024 as well

[flagged]

Huh, is this your first time seeing Anubis? It protects all sorts of sites now!

(By the way: Jackal, not cat.)

Re: We found a division by zero bug in FFmpeg with a vibecoded fuzzer

#250

Post by 21wa »

soiax wrote: post #239

Why are people upvoting a unexploitable bug? How is this interesting? There are thounds of these, no one even reports them unless they are exploitable, DoS only.

Because the fuzzer was vibe coded and stolen by Claude! They only need the headline for celebrating another "AI victory" on Twitter, even though the issue was found in 2024 by OSSFuzz:

https://ffmpeg.org/pipermail/ffmpeg-devel/2024-November/3355...

Post reply on HN