
I don't think anybody actually watches videos any more, so here's MWT's core point -
The flagship and lead vuln in the research is a BSD vuln, it cost $20k to discover with Mythos. Anthropic only reached a crash, and the vuln class in 99%+ cases never reaches RCE, just crashes.
So.. cool.. you spent $20k of VC money to find a crash as the flagship vuln. But... uhm... that isn't the end of the world.
The proof is going to be if any of the open source vulns turn out to be important. So far:
Anthropic set the project across open source projects and provided access and reported the vulns. Typically, you'd expect to see NCSCs spinning up advisories to patch high impact vulns, CISA telling orgs to patch etc etc etc.
What's actually happening is... uhm... a whole heap of nothing but people copy and pasting marketing about how cybersecurity is over.
It's not though, is it?
Well cybersecurity is over but not because of this but because of everyone and their mother deploying openclaw in production...
@agowa338 Cyber security is an insanely complex beast with some parts being technical, some being human, some being regulatory, etc., and well, finding bugs is one small component.
Emphasis on small.
We have not really been great at cyber security in the past, and improvements are needed all across the board. We won't be great at it tomorrow because magic.
Having one component potentially improve is, especially given how speculative the current situation is, is nothing to really worry about. Rather the contrary.
Time will tell, some processes might change, and that is likely all that will happen for a long time.
Most humans in cyber security will very likely notice very little impact for now. Can this all go sideways? Yes, of course. Is it time to say that cyber security is over? I don't think so. At all.
I know. I've been done that. I was the only technician that talked to the compliance people so I "earned" all of the work involved in communicating and bridging both worlds.
And since then it just got worse. Nobody cares about it security. The compliance people are just writing some shit and at this point in many companies they don't even expect their technicians to actually implement it anymore either (if it is even possible at all).
It's just a work creation measure at this point…
@GossiTheDog Haven't we already been there with fuzzing?
Anyway, even if Mythos is as good as they claim, that's not really a problem as long as it is available only to a few. It's when every script kiddie gets access to it that we should start worrying.
@bontchev @GossiTheDog Agreed. Current recommendation from our end:
Keep calm, find and fix bugs, make the world a bit safer one bug at a time...
And ignore the hype train, but keep an open eye on how real and measurable things develop. Just what we did before.
@trademark @azonenberg @GossiTheDog I love how they hype what's a vuln in the in-kernel NFS server (FFS we've been doing this shit at least 2/3 of my lifetime, stop doing NFS/sunrpc shit already) as "FreeBSD RCE".
I knew when I was like 15 that you don't run NFS unless you want to get popped.
@trademark @azonenberg @GossiTheDog Huh? Did your LLM just vomit that? Because it's completely unrelated to what I said.
What I said is that they're hyping a vuln in one small thing, an NFS server, that FreeBSD happens to have a version of that runs in kernelspace, that nobody security-conscious would be using to begin with, and calling it "vuln in FreeBSD!" to make it sound important and impressive.
Absolutely nothing to do with disclosure timeines or whether their findings are real.
@trademark @azonenberg @GossiTheDog They do this to impress investors/C-suites and to keep the grift train going.
I'm not going to address any claims about whether the "technical capabilities of their new model" are a thing.
And to be impressive, yes, they need the thing they attack to be highly regarded in terms of its reputation for security and quality. "Vuln in NFS server module that runs on FreeBSD" does not impress. "Vuln in FreeBSD" does. And it's a lie.
I have no idea how you think this is "insulting to FreeBSD".
@trademark @lispi314 @GossiTheDog @azonenberg We're not making technical recommendations for the FreeBSD team here. Anyone who actually has reason to use NFS knows the risks/tradeoffs and if they're choosing to use something that's going to get them popped that's on them, not on the FreeBSD team.
We're debunking hype that's intentionally exploiting the ignorance of people like yourself about what component was actually vulnerable and whether it's actually something important and noteworthy like Anthropic's propaganda department would have folks believe.
@trademark @lispi314 @GossiTheDog @azonenberg I am debunking the fraudulent importance from misrepresenting what software the vuln was in.
Whether their technical claims are bullshit is another completely legitimate area for debunking but not the one I'm engaged with in this thread.
@trademark @lispi314 @GossiTheDog @azonenberg Running a NFS server in kernelspace is no less backwards than running a httpd in kernelspace (something Linux folks actually tried at one point; it was eventually removed).
Yes there will always be apologists for it. I am not worried about being considered rude when I state that this is just completely untenable from both a security standpoint and a good software engineering standpoint.
@dalias @trademark @azonenberg @GossiTheDog NFS-Ganesha is the userspace server the industry came up with specifically to not run an NFS server in kernelspace anymore.
It still sucks but at least it doesn't compromise the kernel and can actually be run with limited permissions.
In my observation, organizations use these PR announcements & media releases to do layoffs, so they can outsource to a nephew's startup or grandchild's consultancy.
And the necessary patches or policy changes never get implemented.

@GossiTheDog from a practical perspective what worries me more is time to poc/working exploit for known vulns.
OSS library releases patch, model looks at diff + cve description and drops a working exploit for a couple of hundred $ of compute.
Most companies (at least this side of the pond) are not currently equipped to deal with continuously applying patches for 1-day vulns in prod.
Many large orgs here are proud that they've managed to get on a monthly update cycle
@GossiTheDog but other than that... yeah hype-marketing playbook 101.
Didn't OpenAI pull the:"oh no it's too powerful, humanity couldn't take it yet so we're not releasing it to the public", stunt with one of their earlier models as well?^^
Yes, we do watch videos! 🤔
I asked the FreeBSD security officer to compare the (not yet public) one to Coverity reports. Apparently it found something that Coverity didn't, which means at least it isn't just regurgitating static analyser reports.
That said, last time I read the Coverity reports, they found tens of thousands of possible issues (over 90% of the ones I triaged were false positives). You could probably get a higher RoI from paying someone $20K to triage Coverity scan reports.