Follow

πŸŽ‰ We made it! πŸŽ‰

The updated , , and packages are available in right now. Please upgrade and reboot ASAP!

A lot of work went into making this possible πŸ˜€

It's very satisfying to see all my exploits fail β€” and not just in my experimental subhurd, but on the host, running upstream Debian binaries. They just... no longer work, can you believe it?

(That being said, there still are some unpatched vulnerabilities in the Hurd β€” but there's a lot less of them now.)

Β· Β· Tusky Β· 2 Β· 15 Β· 27

@bugaevc Youβ€˜re like Linux, youβ€˜re doing that just for fun, right? πŸ˜‰

@AbbieNormal @bugaevc

I'm curious about the expression "my exploits".

Did you research for bugs and develop proof of concept exploits? πŸ˜€

@neetx @AbbieNormal yes :)

Check out these threads:
β€’ lists.gnu.org/archive/html/bug
β€’ mastodon.technology/@bugaevc/1
β€’ mastodon.technology/@bugaevc/1

P.S. Yes, I know of more yet-unfixed vulnerabilities, and have written some more exploits. Don't let me anywhere near your Hurd boxes :)

@bugaevc @AbbieNormal

Thank you!
So could you now publish a writeup and get a CVE ?

@neetx @AbbieNormal yeah, I could/should.

Unfortunately I haven't heard from β€ͺAmos Jeffries (of squid-cache.org), who has kindly offered to help me with CVE allocation, since June. Maybe it's time to ping him again, or ask someone else to help.

@bugaevc @AbbieNormal

I hope you will publish and get your CVE, good job!

I'd like to know a bit about your workflow in a high level perspective, if I don't bother you

I suppose you virtualized the OS and then did you use static o dynamic analysis?

I'm trying to learn and shift from userland to kernel space exploitation

@neetx @AbbieNormal heh, while I guess I'm legitimately an "independent security researcher" now, keep in mind that I'm just some random guy who happened to stumble on some vulnerabilities.

Yes, my Debian GNU/Hurd installation lives inside qemu/libvirt. No, I didn't use any smart analysis tools: I just browsed the source code and saw things that could go wrong, then wrote exploits for them. It's that simple :)

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!