If your instance is not up to date (see footer), you can pass this along to your admins to check
we think any amount of detail would make it very easy to come up with an exploit
People who would create exploits for this definitely can’t read the diffs and see what changed.
they’re just delaying it by two weeks…
Every barrier that slows down attacks a little is worth it when you are trying to buy time so people can apply emergency updates. It’s not about stopping them from ever figuring it out.
Depends on skill level and the exact nature of the flaw. There’s definitely going to be a nonzero number of malicious people who lie in the middle distance “I can come up with a way to exploit flaws if I have a detailed trail of breadcrumbs” and “I can’t be bothered to do an unlimited amount of work to track down how to do this, I have other malicious things on my schedule for today.”
😬
That’s not good.
That isn’t inversely not un_good, not.
Is this mastodon specific or is it an activitypub flaw?
Mastodon only, and even then only on federated instances.
That’s bad.
I wonder if the companies that forked mastodon (like truth social) will bother to update. I can see someone posting stuff as a former president with this flaw.
Eh, stuff like truth social doesn’t federate with anything anyway, so unfortunately this isn’t a vulnerability for them.
Has it been confirmed this is a federation bug?
Has it been confirmed this is a federation bug?
Based on this commit, which fixes the vulnerability, the bug seems to lie within the ActivityPub receive logic, specifically validation of remote resources.
Oh great, thanks.
Welp. I’m glad Stux was already updating earlier. Honestly, Stux probably knew before just about everyone else
Thanks for the notice. My instance is now updated. :)
