Comment by ranger_danger
15 days ago
> running any sort of Go server like Caddy
It's so much worse than this, and there is a staggering amount of misinformation running rampant about this bug.
MPTCP is not a requirement, it can be exploited merely by sending specially crafted TCP packets with (any) IP options set. No special MPTCP support, web servers or any specific software listeners are even necessary at all to trigger it, just send the packets and boom.
I think the reason people assume MPTCP is a requirement is because that's what the PoC used... but MPTCP itself also doesn't even rely solely on IP options.
Ubuntu also does not even list a single mitigation strategy... at least RHEL did.
And like I said, any normal TCP packet that contains IP (not TCP) options can trigger the bug. I cannot emphasize enough how important and absolutely ridiculous this is.
Like the post says, this is big enough to get a massive amount of people to completely stop trusting Ubuntu entirely and jump ship.
> Ubuntu also does not even list a single mitigation strategy...
I installed newest Ubuntu mainline kernel, it did work for me:
https://kernel.ubuntu.com/mainline/v7.3.1/
I also did patch my FLOSS Go software:
https://github.com/wekan/wekan/commit/e9751b65d4
I'm maintainer of WeKan FLOSS kanban https://wekan.fi , https://github.com/wekan/wekan , and maintainer of FerretDB v1 fork https://github.com/wekan/FerretDB . There is also WeKan Snap package https://snapcraft.io/wekan/ .
But I don't work for Ubuntu, I don't have any answers why Ubuntu does not do something.
I have some publicly facing web servers running Debian and Ubuntu. Specifically, what can I do to test and see if my servers are vulnerable?
Debian (trixie kernel) 6.12.113 was allegedly patched for this bug, but there's also a .115 that's been released in the last few days, upgrade to that and reboot.
For Ubuntu (which I don't use), you'd need a 3rd party updated kernel repo, to use a patched kernel from that.
It's not an instantaneous exploit; it apparently takes a lot of iteration over the network. A lot of cloud network providers are mitigating it by dropping options at the border, but unless you test and confirm that, you should assume it's possible for a motivated-enough attacker to compromise your server.
At least for 26.04, there is a 7.0.0-43 kernel available in the -proposed repos that has the patch. Presumably planned to be made availalbe any month now.
https://wiki.ubuntu.com/Testing/EnableProposed
https://launchpad.net/ubuntu/resolute/amd64/linux-headers-ge...
Someone from Canonical answered about kernel:
https://news.ycombinator.com/item?id=50348688