Noteable: > o3 finds the kerberos authentication vulnerability in 8 of the 100 runs And I'd guess this only became a blog post because the author already knew about the vuln and was just curious to see if the intern could spot it too, given a curated subset of the codebase
He did do exactly what you say – except right after that, while reviewing the outputs, he found that it had also discovered a different 0day.
I used o3 to find a remote zeroday in the Linux SMB implementation
21–30 of 232 posts
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#22Earlier quoted context omitted.
Smb over 25gbit networks - user space samba is much worse there.
This is interesting to me! I regularly deploy 25G network connections, but I don’t think we’d run SMB over that. I am super curious the industry and use case if you’re willing to share!
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#23The article cites a signal to noise ratio of ~1:50. The author is clearly deeply familiar with this codebase and is thus well-positioned to triage the signal from the noise. Automating this part will be where the real wins are, so I'll be watching this closely.
We’ve found a wide range of results and we have a conference talk coming up soon where we’ll be releasing everything publicly so stay tuned for that itll be pretty illuminating on the state of the space
Edit: confusing wording
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#24My understanding is that ksmbd is a kernel-space SMB server "developed as a lightweight, high-performance alternative" to the traditional (user-space) Samba server... Q1: Who is using ksmbd in production? Q2: Why?
2. Samba performance sucks (by comparison) which is why people still regularly deploy Windows for file sharing in 2025.
Anybody know if this supports native Windows-style ACLs for file permissions? That is the last remaining reason to still run Solaris but I think it relies on ZFS to do so.
Samba's reliance on Unix UID/GID and the syncing as part of its security model is still stuck in the 1970s unfortunately.
The caveat is the in-kernel SMB server has been the source of at least one holy-shit-this-is-bad zero-day remote root hole in Windows (not sure about Solaris) so there are tradeoffs.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#25The most interesting and significant bit of this article for me was that the author ran this search for vulnerabilities 100 times for each of the models. That's significantly more computation than I've historically been willing to expend on most of the problems that I try with large language models, but maybe I should let the models go brrrrr!
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#26Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#27Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#28The article cites a signal to noise ratio of ~1:50. The author is clearly deeply familiar with this codebase and is thus well-positioned to triage the signal from the noise. Automating this part will be where the real wins are, so I'll be watching this closely.
We’ve been working on a system that increases signal to noise dramatically for finding bugs, we’ve at the same time been thoroughly benchmarking the entire popular software agents space for this We’ve found a wide range of results and we have a conference talk coming up soon where we’ll be releasing everything publicly so stay tuned for that itll be pretty illuminating on the state of the space Edit: confusing wordin…
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#29The article cites a signal to noise ratio of ~1:50. The author is clearly deeply familiar with this codebase and is thus well-positioned to triage the signal from the noise. Automating this part will be where the real wins are, so I'll be watching this closely.
Re: I used o3 to find a remote zeroday in the Linux SMB implementation
#30Earlier quoted context omitted.
He did do exactly what you say – except right after that, while reviewing the outputs, he found that it had also discovered a different 0day.
Now the question is whether spending same time to analyze that bit of code instead of throwing automated intern at it would be time spent better
What?