Appreciate the full prompt history
Claude wrote a full FreeBSD remote kernel RCE with root shell
11–20 of 128 posts
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#12What about FreeBSD 15.x then? I didn't see anything in the release notes or the mitigations(7) man page about KASLR. Is it being worked on?
NetBSD apparently has it: https://wiki.netbsd.org/security/kaslr/
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#13Key point is that Claude did not find the bug it exploits. It was given the CVE writeup[1] and was asked to write a program that could exploit the bug. That said, given how things are I wouldn't be surprised if you could let Claude or similar have a go at the source code of the kernel or core services, armed with some VMs for the try-fail iteration, and get it pumping out CVEs. If not now, then surely not in a too di…
> have a go at the source code of the kernel or core services, armed with some VMs for the try-fail iteration, and get it pumping out CVEs. FreeBSD kernel is written in C right? AI bots will trivially find CVEs.
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#14The talk "Black-Hat LLMs" just came out a few days ago: https://www.youtube.com/watch?v=1sd26pWhfmg Looks like LLMs are getting good at finding and exploiting these.
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#15Earlier quoted context omitted.
> have a go at the source code of the kernel or core services, armed with some VMs for the try-fail iteration, and get it pumping out CVEs. FreeBSD kernel is written in C right? AI bots will trivially find CVEs.
The Morris worm lesson is yet to be taken seriously.
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#16Appreciate the full prompt history
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#17Earlier quoted context omitted.
> Credits: Nicholas Carlini using Claude, Anthropic Claude was used to find the bug in the first place though. That CVE write-up happened because of Claude, so while there are some very talented humans in the loop, Claude is quite involved with the whole process.
> Claude was used to find the bug in the first place though. That CVE write-up happened because of Claude Do you have a link to that? A rather important piece of context. Wasn't trying to downplay this submission the way, the main point still stands: But finding a bug and exploiting it are very different things. Exploit development requires understanding OS internals, crafting ROP chains, managing memory layouts, deb…
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#18I'm just gonna assume it was asked to fix some bug and it wrote exploit instead
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#19Key point is that Claude did not find the bug it exploits. It was given the CVE writeup[1] and was asked to write a program that could exploit the bug. That said, given how things are I wouldn't be surprised if you could let Claude or similar have a go at the source code of the kernel or core services, armed with some VMs for the try-fail iteration, and get it pumping out CVEs. If not now, then surely not in a too di…
> Credits: Nicholas Carlini using Claude, Anthropic Claude was used to find the bug in the first place though. That CVE write-up happened because of Claude, so while there are some very talented humans in the loop, Claude is quite involved with the whole process.
Re: Claude wrote a full FreeBSD remote kernel RCE with root shell
#20The talk "Black-Hat LLMs" just came out a few days ago: https://www.youtube.com/watch?v=1sd26pWhfmg Looks like LLMs are getting good at finding and exploiting these.
Everybody is acts so surprised as if nobody (around here of all places!) read the sama tweet in which he was hiring the Head of Preparedness... in December. https://xcancel.com/sama/status/2004939524216910323